There have been multiple accounts created with the sole purpose of posting advertisement posts or replies containing unsolicited advertising.

Accounts which solely post advertisements, or persistently post them may be terminated.

[Solved] Sudden Issues

Suddenly, things aren’t loading properly. For example Heimdall takes forever to load and Navidrome is timing out.

When I do docker-compose pull

It says says

Error response from daemon: Get “https://registry-1.docker.io/v2/” net/http: request cancelled while waiting for connection (Client.Timeout exceeded while awaiting headers)

Anyone know what’s up or how to fix it?

Edit: checking the /etc/resolv.conf

It says


<span style="color:#323232;">search cable.virginm.net
</span><span style="color:#323232;">nameserver 194.168.4.100
</span><span style="color:#323232;">nameserver 194.168.8.100
</span>

Though neither are opening anything from a browser

Not sure if it’s helpful, but this is what the networking bridge says via Portainer


<span style="color:#323232;">Network details
</span><span style="color:#323232;">
</span><span style="color:#323232;">Name: bridge
</span><span style="color:#323232;">Id: Oc3f5ce6ffc566ee80/1689056f11d491269849967877933858053581742-978
</span><span style="color:#323232;">Driver: bridge
</span><span style="color:#323232;">Scope: local
</span><span style="color:#323232;">Attachable: false
</span><span style="color:#323232;">Internal: false
</span><span style="color:#323232;">IPV4 Subnet - 172.120.0/16: IPV4 Gateway - 172.17.0.1
</span><span style="color:#323232;">IPV4 P Range: PV4 Excluded IPs
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">Access control
</span><span style="color:#323232;">
</span><span style="color:#323232;">Ownership: public
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">Network options
</span><span style="color:#323232;">
</span><span style="color:#323232;">com.docker network.bridge default_bridge: true
</span><span style="color:#323232;">com.docker.network.bridge.enable.icc: true
</span><span style="color:#323232;">com docket.network.bridge.enable_ip.masquerade: true
</span><span style="color:#323232;">com docker.network.bridge.host_binding_ipv4: 0.0.0.0
</span><span style="color:#323232;">com.docker.network.bridge.name: docker0
</span><span style="color:#323232;">com.docker.network.driver.mtu: 1500
</span>

I suspect it may be this bug github.com/moby/moby/issues/47662

# Turns out it was just Virgin Media’s router doing shit. A factory reset of the router fixed my issues.

bjornsno ,

I started seeing this too. Interestingly pulling individual images works, it only does this when trying to pull all the images.

sabreW4K3 OP ,
@sabreW4K3@lazysoci.al avatar

That sounds like it could be load issue. That maybe checking your router could fix your issues as it did mine.

taaz ,

I would try momentarily replacing the defined dns servers with nameserver 1.1.1.1 and see if stuff improves, though the pull error would hint that docker did resolve the name but somehow didn’t get an answer.
Hard to guess what else could be a problem apart from some obvious stuff - check if the internet connection is healthy and stable (ping, watch for spikes in ms or drops, also any outgoing firewall filters?)

sabreW4K3 OP ,
@sabreW4K3@lazysoci.al avatar

Just want to say thank you for your kindness!

sznowicki ,

So it was DNS?

sabreW4K3 OP ,
@sabreW4K3@lazysoci.al avatar

Either DNS or DHCP

AtariDump ,
  • All
  • Subscribed
  • Moderated
  • Favorites
  • [email protected]
  • random
  • lifeLocal
  • goranko
  • All magazines