Skip to content
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

Docker never ends the 'starting' point #360

Closed
nicholas-raphael-farias opened this issue Aug 18, 2016 · 4 comments
Closed

Docker never ends the 'starting' point #360

nicholas-raphael-farias opened this issue Aug 18, 2016 · 4 comments

Comments

@nicholas-raphael-farias

Expected behavior

Actual behavior

Information

Diagnostic ID: 67485CA9-D735-4D5C-B2C4-FBE5EDC602D4
Docker for Mac: 1.12.0-a (Build 11213)
macOS: Version 10.10.5 (Build 14F1713)
[ERROR] docker-cli
docker ps failed
[OK] app
[OK] moby-syslog
[ERROR] disk
disk check failed with: Failure("exec: /Applications/Docker.app/Contents/Resources/bin/../../../Contents/MacOS/qemu-img check /Users/Raphel/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/Docker.qcow2 > /tmp/67485CA9-D735-4D5C-B2C4-FBE5EDC602D4/20160818-184415/qemu-img-check.stdout 2> /tmp/67485CA9-D735-4D5C-B2C4-FBE5EDC602D4/20160818-184415/qemu-img-check.stderr: exit 2")
[OK] virtualization
[OK] system
[OK] menubar
[OK] osxfs
[OK] db
[OK] slirp
[OK] moby-console
[OK] logs
[OK] vmnetd
[OK] env
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

  1. ...
  2. ...
@mihirv0ra
Copy link

Please check #370 i was able to get this resolved, by going to Preferencec -> Uninstall/Reset -> Reset , note that it cleans up all the containers and images

@mchiang0610
Copy link

Merging with #119

@samoht
Copy link
Contributor

samoht commented Oct 12, 2016

Detected symptom of problem 'symlinks-are-not-correctly-installed' in 67485CA9-D735-4D5C-B2C4-FBE5EDC602D4/20160818-185205.

Thanks for your report! The docker symlinks have not been correctly installed by the installer, which is a known issue that we are currently working on. A possible workaround is to install the docker client manually by running:

ln -s ~/Library/Group\ Containers/group.com.docker/bin/docker /usr/local/bin/docker

May be related to #785

The following log matches:

Aug 18 17:55:30 MacBook-Pro-2.local Docker[com.docker.vmnetd][11757] <Critical>: File /var/run/docker.sock is a symlink or a socket
Aug 18 17:55:30 MacBook-Pro-2.local Docker[com.docker.vmnetd][11757] <Notice>: User 501 has container folder /Users/Raphel/Library/Containers/com.docker.docker/Data/s60
Aug 18 17:55:30 MacBook-Pro-2.local Docker[com.docker.vmnetd][11757] <Critical>: File /var/run/docker.sock is a symlink or a socket
Aug 18 17:55:30 MacBook-Pro-2.local Docker[com.docker.docker][11722] <Error>: Symlinks are not correctly installed.
Aug 18 17:55:31 MacBook-Pro-2.local Docker[com.docker.docker][11722] <Notice>: com.docker.osx.hyperkit.linux launched with PID 11761
Aug 18 17:55:32 MacBook-Pro-2.local Docker[com.docker.frontend][11760] <Critical>: dial unix /Users/Raphel/Library/Containers/com.docker.docker/Data/s20: connect: no such file or directory
Aug 18 17:55:33 MacBook-Pro-2.local Docker[com.docker.docker][11722] <Error>: frontend process failed
Aug 18 17:55:33 MacBook-Pro-2.local Docker[com.docker.osx.hyperkit.linux][11761] <Notice>: Acquired task manager lock

@docker-robott
Copy link
Collaborator

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

@docker docker locked and limited conversation to collaborators Jun 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants