Docker client on MacOS failed to boot

[robert-bor]

After Docker starts, it immediately throws an error:

Docker for Mac: version: 1.13.1 (94675c5a7)
macOS: version 10.12.3 (build: 16D32)
logs: /tmp/07D3CEA4-D41E-406C-9DB4-5F98DA209D80/20170301-095024.tar.gz
failure: com.docker.slirp is not running
[OK]     vmnetd
[OK]     dns
[ERROR]  driver.amd64-linux
com.docker.driver.amd64-linux -db is not running
[OK]     virtualization VT-X
[OK]     app
[ERROR]  moby
/Users/XXX/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/console-ring does not exist
[OK]     system
[OK]     moby-syslog
[ERROR]  db
Connection refused (ECONNREFUSED) connecting to /Users/XXX/Library/Containers/com.docker.docker/Data/s40: check if service is running
com.docker.db is not running
[OK]     env
[OK]     virtualization kern.hv_support
[ERROR]  slirp
Unexpected error ((Failure
"Error connecting socket to 9p endpoint unix:/Users/XXX/Library/Containers/com.docker.docker/Data/s51: Unix.Unix_error(Unix.ECONNREFUSED, \"connect\", \"\")")) connecting to /Users/XXX/Library/Containers/com.docker.docker/Data/s51
com.docker.slirp is not running
slirp check failed with: (Failure
"Error connecting socket to 9p endpoint unix:/Users/XXX/Library/Containers/com.docker.docker/Data/s52: Unix.Unix_error(Unix.ECONNREFUSED, \"connect\", \"\")")
[ERROR]  osxfs
com.docker.osxfs is not running
[OK]     moby-console
[OK]     logs
[ERROR]  docker-cli
Connection refused (ECONNREFUSED) connecting to /var/run/docker.sock: check if service is running
Connection refused (ECONNREFUSED) connecting to /Users/XXX/Library/Containers/com.docker.docker/Data/s60: check if service is running
docker ps failed
[OK]     menubar
[OK]     disk

The solution in https://github.com/docker/for-mac/issues/1006 is to activate Docker Client > Preferences > Reset > Reset to factory defaults:

Just clicking on "reset" did the trick for me as well - no reinstall needed. You just have to be really fast when clicking through the reset buttons to be faster than the error message of the booting docker container because the error dialog blocks all other input.

This worked.