Comment on How do I stop Docker trying to pull from IPv6?
tychosmoose@piefed.social 3 days ago
Docker is a distraction in your problem description.
It's like if you asked why the top gear in your car isn't working and gave the model of car and engine type and gearbox. But it's really that you're stuck in slow traffic. Focus on the road name and destination to find a faster route.
For your problem, search for how to disable ipv6 for the Linux distribution and version that you have installed. You will find lots of guidance. Or share those details here for someone to help.
Or, better might be to see if there is a way to get ipv6 tunneling working on your connection. It may be possible even if the ISP is unhelpful.
Zagorath@aussie.zone 3 days ago
Except if I try and access the same domain using curl, it works fine. For some reason, Docker specifically is what’s failing.
tychosmoose@piefed.social 3 days ago
Different programs have different defaults.
But in your situation which would be more helpful - prevent this one docker command from using ipv6 (likely more difficult), or preventing all commands from using your broken ipv6 config (likely easier)?
I have no idea about the first. Maybe some people know this detail. But I'm sure that with a distro and version that you're running, there are lots of people who could help with the second. Raspberry Pi 3B+ is the hardware. What software are you using?
Zagorath@aussie.zone 3 days ago
Whatever the latest version of Raspbian was a month or two ago when I installed it.
uname -a
outputs[…]6.12.25+rpt-rpi-v8[…]
./etc/os-release
contains “Debian GNU/Linux 12 (bookworm)”.tychosmoose@piefed.social 3 days ago
Ok, so it's probably using NetworkManager. I would try disabling it in /etc/NetworkManager/NetworkManager.conf by adding a block like:
Then
sudo systemctl restart NetworkManager
.Can't say for sure if this will work. I dislike using NetworkManager on my servers so I can't test if this works. But hopefully the before/after of
ip addr
is different.Although it looks like your
ip addr
output posted an hour or so ago doesn't show any ipv6 addressing. Maybe the problem is solved now.