upgrade install failure on mac, running upon system restart

[moorage]

Expected behavior

Actual behavior

Information

Diagnostic ID: 9351DC48-2460-4654-9A31-6ACD7600A493
Docker for Mac: 1.12.0-beta21 (Build 10868)
macOS: Version 10.11.5 (Build 15F34)
[ERROR] docker-cli
Connection refused (ECONNREFUSED) connecting to /var/run/docker.sock: check if service is running
Connection refused (ECONNREFUSED) connecting to /Users/thrivesmart1/Library/Containers/com.docker.docker/Data/s60: check if service is running
docker ps failed
[OK] app
[OK] moby-syslog
[OK] disk
[OK] virtualization
[OK] system
[OK] menubar
[ERROR] osxfs
com.docker.osxfs is not running
[ERROR] db
Connection refused (ECONNREFUSED) connecting to /Users/thrivesmart1/Library/Containers/com.docker.docker/Data/s40: check if service is running
com.docker.db is not running
[ERROR] slirp
Connection refused (ECONNREFUSED) connecting to /Users/thrivesmart1/Library/Containers/com.docker.docker/Data/s51: check if service is running
com.docker.slirp is not running
[OK] moby-console
[OK] logs
[OK] vmnetd
[OK] env
[OK] moby
[ERROR] driver.amd64-linux
Docker.app/Contents/MacOS/com.docker.driver.amd64-linux -db is not running

Steps to reproduce

1. ...
2. ...

[djs55]

It looks like a problem talking to the privileged helper component com.docker.vmnetd:

Aug  2 22:08:40 ... Docker[com.docker.vmnetd][2528] <Critical>: client requests com.docker.vmnetd uninstall
Aug  2 22:08:40 ... Docker[com.docker.vmnetd][2528] <Critical>: com.docker.vmnetd uninstall complete
Aug  2 22:08:40 ... Docker[com.docker.docker][2517] <Notice>: com.docker.vmnetd automatic uninstall successful
Aug  2 22:08:40 ... Docker[com.docker.vmnetd][2528] <Critical>: Deleted /var/tmp/com.docker.vmnetd.socket
Aug  2 22:08:47 ... kernel[kern][0] <Notice>: hfs: unmount initiated on Docker on device disk3s1
Aug  2 22:08:48 ... Docker[com.docker.docker][2517] <Notice>: privileged installation of com.docker.vmnetd successful
Aug  2 22:08:48 ... Docker[com.docker.docker][2517] <Critical>: Communication with networking components failed.
Aug  2 22:08:48 ... Docker[com.docker.vmnetd][2537] <Notice>: com.docker.vmnetd starting

Given that the com.docker.vmnetd process started up after the Communication with networking components failed and that the diagnostics reported being able to connect to com.docker.vmnetd I suspect this is a race between the install code and the initial connection code in the UI.

[synic]

I don't know if this is the same issue, however, I still have to do this every time I install a docker update (even the one today, beta26):

$ sudo chmod 600 /Library/LaunchDaemons/com.docker.vmnetd.plist
$ sudo launchctl load /Library/LaunchDaemons/com.docker.vmnetd.plist

If I do not do this, docker will just hang and all the menu items will be greyed out. If I kill it and restart, it will ask for my password again, and fail again. If I do the above steps, everything is great.

I've got an early 2015 Macbook Pro running 10.11.6

[dave-tucker]

Thanks for the report @synic.
Next time it happens, have a look (using Expose) for any stray Docker for Mac modal dialogs. There are cases where these appear behind other windows and then the symptoms will be exactly as you describe - menu buttons greyed out, app frozen.

[dave-tucker]

The race described by @djs55 should have been fixed in Beta 26 and Stable 1.12.1 so I'm going to close this for now. If we get new reports, then I'll re-open so we can investigate further.

[synic]

@dave-tucker: This happened again in Version 1.12.2-rc1-beta27 . The permissions were wrong again.

I don't know if I'm reporting the bug correctly, because you've stated that it's been fixed several times (once here, several times on the docker forums), but it has never changed.

After installing docker, permissions of /Library/LaunchDaemons/com.docker.vmnetd.plist are too permissive. Docker will not start without freezing, and there is no hidden dialog.

Trying to load it manually, you will get the following error:

[LaunchDaemons]$ sudo launchctl load com.docker.vmnetd.plist
/Library/LaunchDaemons/com.docker.vmnetd.plist: Path had bad ownership/permissions

This happens with every single update on my machine. Changing permissions to 600 immediately fixes it.

[crates]

I was having this issue just now, and setting the owner to root:admin and the perms to 644 fixed it.

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked