-
Notifications
You must be signed in to change notification settings - Fork 262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DNS lookups broken in 3.14 (minikube & mac using virtualbox) #185
Comments
On the positive side it seems to work for minikube using --driver=hyperkit and --hyperkit-vpnkit-sock (needed because of VPN) |
It's not mac only, I have the same problem (3.12 worked, 3.13 and 3.14 did not) on a Windows host. If I ran
If I force docker to ignore the my host system DNS settings and use Google it works fine.
I then realised that I try running I then disable IPv6 completely on my Ethernet adapter and everything works fine. I suspect there might be an issue with my cheap router and IPv6 (in my own personal case). Try disabling IPv6 on your machine and see if that does anything.
I believe it's because 3.13 and 3.14 use a new version of musl-1.2.1-r1 or busybox-1.32.0-r2 as per this: |
I'm seeing similar behavior on Linux on my raspberry pi 3 (armv7l). Rolling back to 3.12.3 resolves the issue. However, specifying the DNS argument to the docker CLI does not resolve the issue for me, nor does specifying it in the daemon.json config file. I did no testing with IPv6 vs IPv4, so cannot attest to that scenario. |
I think I've run into the same problem. When running 3.13 I get a |
Apologies for yet another DNS lookup issue but I am out of options.
As I see now (for example) there is now a
7.3.29-fpm-alpine3.14
docker image but no7.3.29-fpm-alpine3.12
because it is expected that we drop support for alpine 3.12.When we are using alpine 3.13 and 3.14 inside
minikube
locally for mac with the driver ofvirtualbox
we have the same issue that others reported. Dns resolving does not behave the same as 3.12If inside the /etc/resolv.conf we leave the original nameserver defined from k8s (lets assume 10.96.0.10) then we can access the internal k8s services but not the internet.
If inside the /etc/resolv.conf we add nameserver 8.8.8.8 then a container can access the internet but not the k8s internal services.
I really can not pinpoint the following:
The text was updated successfully, but these errors were encountered: