New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
create dev environment failed: Cannot connect to the Docker daemon at unix:///var/run/docker.sock #6531
Comments
Workaround
find ./Library -name "*docker*" 2> /dev/null
...
rm -rf './Library/Application Support/com.bugsnag.Bugsnag/com.docker.docker'
rm -rf './Library/Application Support/com.bugsnag.Bugsnag/com.docker.docker/v1/KSCrashReports/Docker-CrashState.json'
rm -rf './Library/Preferences/com.electron.dockerdesktop.plist'
rm -rf './Library/Preferences/com.docker.docker.plist'
rm -rf './Library/Application Scripts/group.com.docker'
rm -rf './Library/HTTPStorages/com.docker.docker'
rm -rf './Library/Logs/Homebrew/docker'
rm -rf './Library/Group Containers/group.com.docker'
It's possible you would need to kill and re-create a dev environment (from folder or github), but it would still work... |
Thanks for the report! we're talking about this internally. We removed the /var/run symlink but dev environments was still using it. More discussion here: #6529 Another workaround is to manually create the symlink:
|
This should be fixed in v4.13.1 |
I just updated to v4.16.2 and hit this issue.
The above did resolve the issue for me. But it appears that this regressed in v4.16.2. |
In version v4.16.2 the issue is appearing too. |
Another for v4.16.2. As my Mac is managed by corporate, I can't add the symlink due to permissions issues so am currentl y unable to use. |
I was running into this on Check your In my case, removing |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. /lifecycle locked |
Expected behavior
Expect to see no error when create new dev environment from local folder (or public github repo).
Actual behavior
P.S. Can this command just fine:
Information
Output of
/Applications/Docker.app/Contents/MacOS/com.docker.diagnose check
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: