2 ms·
Nobody should ever mess with a system's resolver settings. I've recently had to debug a bug with a container (probably not Docker itself) unable to reach the i
by kccqzy 3y ago
Nobody should ever mess with a system's resolver settings.
I've recently had to debug a bug with a container (probably not Docker itself) unable to reach the internet. It turns out the machine is behind a NAT64 and has IPv6 addresses only, yet something in the container helpfully reconfigures the resolver to be 8.8.8.8 which of course is unreachable.
- Bluecobra 3y agoUbuntu on WSL is really bad about this and you have to end up using chattr to make /etc/resolv.conf immutable to prevent it from fiddling around with it. Really makes you appreciate Slackware/FreeBSD.
- patrakov 3y agoRunning anything on NAT64 without 464XLAT is a broken setup.
- deleted 3y ago[deleted]
- raffraffraff 3y agoI have to admit with some embarrassment that I've never deployed an ipv6-only infrastructure, so I've never had to figure this stuff out. 25+ years doing Linux/infra and it's still arcane and avoidable. I don't even know what 464XLAT is, and have to look it up. > 464XLAT allows private IPv4 clients to connect to an IPv4 host over an IPv6 network. It only supports client-server, not peer-to-peer communication or inbound connections. ...A brief description for anyone else who didn't know.