Comment on How do I stop Docker trying to pull from IPv6?
Zagorath@aussie.zone 3 days agoUnfortunately not.
docker run hello-world Unable to find image 'hello-world:latest' locally docker: Error response from daemon: Get "https://registry-1.docker.io/v2/library/hello-world/manifests/sha256:ec153840d1e635ac434fab5e377081f17e0e15afab27beb3f726c3265039cfff": dial tcp [2600:1f18:2148:bc00:eff:d3ae:b836:fa07]:443: connect: network is unreachable Run 'docker run --help' for more information
tychosmoose@piefed.social 3 days ago
Well crap. Do you have no ipv6 address now in
ip addr
?Guess I gave Docker too much benefit of the doubt and assumed it should failover to v4 once v6 was disabled. Bad assumption on my part.
Could it be a DNS problem? If you
dig registry-1.docker.io +short
does it return an ipv4 or v6 address?It looks like there have been sporadic reports of problems from people since last year.
MysteriousSophon21@lemmy.world 2 days ago
Try adding
{“ipv6”: false}
to your/etc/docker/daemon.json
file (create it if it doesnt exist), then restart docker withsudo systemctl restart docker
- this forces docker to use IPv4 only.tychosmoose@piefed.social 2 days ago
This flag seems to only disable ipv6 on the default Docker bridge network, not daemon-wide. At least per this discussion.
Zagorath@aussie.zone 3 days ago
Just comparing it by eye, there’s no change.
But if I ping it
tychosmoose@piefed.social 3 days ago
It's in the dnsutils package.
Zagorath@aussie.zone 2 days ago