DNS resolution fails after a few minutes of Docker running. I can do a ‘docker build’ normally one minute, then after a while it stops working. Looking at the logs I can see that I am timing out trying to resolving a yum repo, for example.
25/05/2016 14:36:38.885 Docker[638]: recvfrom failed with Lwt.Canceled
25/05/2016 14:36:38.885 Docker[638]: DNS response timed out after 5s
25/05/2016 14:36:38.885 Docker[638]: DNS response timed out after 5s
Logging into the Moby VM with screen gives me the same resolution issues:
moby:~# ping www.google.com
ping: bad address ‘www.google.com'
Information
Extra interfaces seem to have appeared in the VM its broken state. The ‘vethXXX’ interfaces were not there before dns failed.
docker0 Link encap:Ethernet HWaddr 02:42:39:7D:43:B3
inet addr:172.17.0.1 Bcast:0.0.0.0 Mask:255.255.0.0
inet6 addr: fe80::42:39ff:fe7d:43b3%32656/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13180 errors:0 dropped:0 overruns:0 frame:0
TX packets:27950 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:544710 (531.9 KiB) TX bytes:40868424 (38.9 MiB)
eth0 Link encap:Ethernet HWaddr C0:FF:EE:C0:FF:EE
inet addr:192.168.65.2 Bcast:0.0.0.0 Mask:255.255.255.248
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:28252 errors:0 dropped:0 overruns:0 frame:0
TX packets:13497 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:41018031 (39.1 MiB) TX bytes:762028 (744.1 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1%32656/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:5 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:245 (245.0 B) TX bytes:245 (245.0 B)
veth33a8c93 Link encap:Ethernet HWaddr F2:30:32:F9:E5:27
inet6 addr: fe80::f030:32ff:fef9:e527%32656/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:65 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:648 (648.0 B) TX bytes:4726 (4.6 KiB)
vethfd6e21f Link encap:Ethernet HWaddr 66:A5:B7:D3:51:DF
inet6 addr: fe80::64a5:b7ff:fed3:51df%32656/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:49 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:648 (648.0 B) TX bytes:3430 (3.3 KiB)
OS X: version 10.11.5 (build: 15F34)
Docker.app: version v1.11.1-beta13
Running diagnostic tests:
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160527-150301.tar.gz
Most specific failure is: No error was detected
Your unique id is: 4CDDD2F7-C691-46DF-9DEF-F4174674116C
Steps to reproduce the behavior
- Start docker
- Wait for about 30 minutes
- Try a docker build or ping www.google.com from Moby VM