Expected behavior
DNS to resolve
Actual behavior
DNS doesn’t work
Information
In the Docker Logs I am getting
DNS response timed out after 5s
This happens when i try to hit an internet address. I am not behind any VPNs
Share and learn in the Docker community.
DNS to resolve
DNS doesn’t work
In the Docker Logs I am getting
DNS response timed out after 5s
This happens when i try to hit an internet address. I am not behind any VPNs
I am experiencing a similar thing, PFI the details and check if its similar:
I noticed this when i was trying to do a apk add on an alpine container. It couldn’t find the upgrade URL.
I’m also running into a DNS resolving issue, but only when I’m running behind our corporate AnyConnect VPN.
I’m running beta11, but it’s been happening since I started the beta around beta8. This also happens for a coworker on the same VPN.
This happens for both external (docker.io) as well as our private registry (not accessible from public internet).
My syslog has the following:
May 11 11:05:06 axxxx-mbp Docker[377] : DNS response timed out after 5s
My VPN has the following settings:
Protocol Info Active Protocol Protocol Cipher: RSA_AES_256_SHA1 Protocol Compression: None Protocol State: Connected Protocol: DTLS Inactive Protocol Protocol Cipher: RSA_RC4_128_SHA1 Protocol Compression: None Protocol State: Connected Protocol: TLS
Routes Secure Routes 10.1.101.0 24 10.1.102.0 24 10.1.103.0 24 10.1.104.0 24 10.1.105.0 24 10.1.106.0 24 10.1.107.0 24 10.1.130.0 24 10.1.20.0 24 10.1.3.0 24 10.1.60.0 24 10.1.10.0 24 10.1.61.0 24 10.1.62.0 24 10.1.254.234 32 10.1.254.235 32 10.1.254.236 32 10.1.254.237 32 10.1.254.238 32 10.1.254.232 32 10.1.254.233 32 xx.xx.128.0 24 xx.xxx.40.64 26 10.1.108.0 24 10.1.64.0 24 10.40.0.0 16 10.1.33.0 24 10.1.37.0 24 10.1.109.0 24 10.5.0.0 16 10.6.0.0 16 10.12.0.0 16 10.11.0.0 16 10.10.0.0 16 10.4.0.0 16 Non-tunneled Routes 0.0.0.0 0Firewall Rules
OS Version Mac OS X 10.11.4
I unfortunately don’t know enough about Mac internals to troubleshoot very much. Can I connect to the xhyve VM like I could the old docker-machine way to see if check DNS resolution there?
Edit to add docker info:
Containers: 0 Running: 0 Paused: 0 Stopped: 0 Images: 2 Server Version: 1.11.1 Storage Driver: aufs Root Dir: /var/lib/docker/aufs Backing Filesystem: extfs Dirs: 4 Dirperm1 Supported: true Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: bridge null host Kernel Version: 4.4.9-moby Operating System: Alpine Linux v3.3 OSType: linux Architecture: x86_64 CPUs: 2 Total Memory: 1.955 GiB Name: moby ID: F6JI:IJNQ:OD5P:JAOO:DVI3:C67J:EM6C:xxxx:xxxx:xxxx:xxxx:xxxx Docker Root Dir: /var/lib/docker Debug mode (client): false Debug mode (server): true File Descriptors: 16 Goroutines: 34 System Time: 2016-05-11T15:09:43.573045785Z EventsListeners: 1 Registry: https://index.docker.io/v1/
I have the same issue: Docker says “No upstream DNS server configured”. After a reboot of the Mac it always works, but after some time (i think after a sleep) it doesn’t work anymore.
I’ve got the same issue on Mac OS while trying to run multicontainer playframework (java) application:
<Error>: recvfrom failed with Lwt.Canceled
<Error>: DNS response timed out after 5s
<Error>: Socket.TCPV4.read 23.59.89.174:443: caught Unix.Unix_error(Unix.ECONNRESET, "read", "") returning Eof
I could run the application after all, but it was too slow and only worked after Nth try.