Docker Community Forums

Share and learn in the Docker community.

Docker.local stops working even when xhyve vm is still running


(Rick Peters) #1

Expected behavior

ping docker.local should always give a response when docker for mac is running (in nat mode)

Actual behavior

after a while it seems that docker.local stops working, even though the address of the current running VM is working.
If I do a ping 192.168.64.1 or a ping 192.168.64.x (where x is the current interation of the VM I guess) they both give response.

Doing a pinata restart does not solve the problem. After restarting my computer everything works again, but the ip-adress of the current docker daemon is 1 higher then before.

I don’t know what the role is of the 192.168.64.1 address, but this always work. It’s just the docker.local that does not resolve anymore. Furthermore I think it’s strange that the ip-address of the VM itself keeps increasing (right now I am already on 192.168.64.6).

Information

pinata diagnose shows nothing special.

OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.10.3-beta5
Running diagnostic tests:
[OK] docker-cli
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] lofs
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160405-114435.tar.gz.
Your unique id in bugsnag is: 5493AAF3-94DB-4093-84EF-3CF757B5B3A5

Steps to reproduce the behavior

I don’t know how to reproduce, but I have the distinct feeling that things go wrong after my mac has either been in sleep mode or changed wifi-networks with a longer time in between the starts.