After exiting the Docker app, the com.docker.vmnetd process remains running. Some curious users, like myself, intend to kill processes they are not sure of…
> ps -ef | grep docker
322: 0 8172 1 0 1:19pm ?? 0:00.01 /Library/PrivilegedHelperTools/com.docker.vmnetd
351: 501 8817 8127 0 1:55pm ttys007 0:00.00 grep --color=auto --line-number docker
> sudo kill 8172
> ps -ef | grep docker
350: 501 8821 8127 0 1:55pm ttys007 0:00.01 grep --color=auto --line-number docker
0 %> sudo kill 8172
kill: 8172: No such process
After killing it, the socket remained, and I’ve removed it it also:
> sudo netstat -an | grep vmnet
289:dfd10dd385f02057 stream 0 0 dfd10dd39158ff67 0 0 0 /var/tmp/com.docker.vmnetd.socket
> sudo rm -f /var/tmp/com.docker.vmnetd.socket
Next, launching Docker app promps for password and fails to start. This is what I see in the logs:
Apr 29 13:56:55 wroom Docker[8852] <Notice>: Application version: 1.11.0-beta9 (6388)
Apr 29 13:56:55 wroom Docker[8852] <Notice>: OSX Version: Version 10.11.4 (Build 15E65)
Apr 29 13:56:55 wroom Docker[8852] <Notice>: migrator: start migration process
Apr 29 13:56:55 wroom Docker[8852] <Notice>: migrator: previous install detected
Apr 29 13:56:55 wroom Docker[8852] <Notice>: migrator: previous version is 1.11.0-beta9
Apr 29 13:56:55 wroom Docker[8852] <Notice>: migrator: no migration needed, you are good to go!
Apr 29 13:56:55 wroom Docker[8852] <Notice>: migrator: end of migration process
Apr 29 13:56:55 wroom Docker[8852] <Notice>: event tracker initialized
Apr 29 13:56:55 wroom Docker[8852] <Notice>: Limited access: checking...
Apr 29 13:56:55 wroom Docker[8852] <Notice>: Bundle path: /Users/ilya/Applications/Docker.app
Apr 29 13:57:01 wroom Docker[8852] <Notice>: privileged installation of com.docker.vmnetd successful
Apr 29 13:57:01 wroom Docker[8852] <Critical>: Communication with networking components failed.
Apr 29 13:57:06 wroom Docker[8852] <Notice>: applicationWillTerminate
And the socket doesn’t happen to reappear:
> ls -la /var/tmp/com.docker.vmnetd.socket
ls: /var/tmp/com.docker.vmnetd.socket: No such file or directory
This doesn’t seem to be critical, but may be more graceful handling may be required…