Same problem. Fresh install. Factory reset does not help.
Factory reset solves the problem for Version 1.12.0-rc2-beta17 (build: 9779)
ff18c0c63c5ff3c4a4a925d191d5592d655779d7 also.
Quitting docker and then killing all process containing “docker” did the trick for me. To be safe, I recreated the symlink as mentioned earlier in this thread.
Quitting docker and killing all processes works. No need to recreate the symlink (at least here). Thanks @shoan!
Quitting docker and killing all processes does not work for me. Factory Reset is the only thing that worked.
Here’s a script to do this quickly.
for e in `compgen -A variable | grep DOCKER_`; do unset $e; done
Factory reset did not help me. Did not have environment variables set. Docker appears to be setting the symlink incorrectly to a socket that doesn’t exist. @austinylin’s suggested work-around works for me. Running Version 1.12-0-beta22 (build:11222).
still got this problem.
the is a clean install.
Version 1.12.0-a (build: 11213)
ad6ab836187e4111082447b7c0a6a74d01929a5c