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

The installer can let the system in a half-working state #785

Closed
dunkenbutterfly opened this issue Oct 11, 2016 · 2 comments
Closed

The installer can let the system in a half-working state #785

dunkenbutterfly opened this issue Oct 11, 2016 · 2 comments

Comments

@dunkenbutterfly
Copy link

dunkenbutterfly commented Oct 11, 2016

Expected behavior

docker info returns info

Actual behavior

bash: docker: command not found

Information

  • Full output of the diagnostics from "Diagnose & Feedback" in the menu
  • A reproducible case if this is a bug, Dockerfiles FTW
  • Page URL if this is a docs issue or the name of a man page

Docker for Mac: version: 1.12.2-rc1-beta27 (179c18c)
OS X: version 10.12 (build: 16A323)
logs: /tmp/F637D9FB-3F4F-46B5-B1E5-FEACF0C16CE0/20161011-232145.tar.gz
20161011-232145.tar.gz

failure: cannot find docker
[ERROR] docker-cli
cannot find docker
docker-cli check failed with: Failure("docker -v: timeout after 10.00s")
[OK] virtualization kern.hv_support
[OK] menubar
[OK] moby-syslog
[OK] dns
[OK] disk
[OK] system
[OK] app
[OK] osxfs
[OK] virtualization VT-X
[OK] db
[OK] slirp
[OK] logs
[OK] env
[OK] vmnetd
[OK] moby-console
[OK] moby
[OK] driver.amd64-linux
Failure: Could not upload diagnostic data to remote server (docker-diagnose exit code is 1)

Steps to reproduce the behavior

  1. docker info
  2. ...
@samoht
Copy link
Contributor

samoht commented Oct 12, 2016

Detected symptom of problem 'symlinks-are-not-correctly-installed' in F637D9FB-3F4F-46B5-B1E5-FEACF0C16CE0/20161011-232145.

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

The following log matches:

Oct 11 21:58:12 MacBook-Pro-di-ovanni Docker[com.docker.vmnetd][6727] <Notice>: Client supplied container path /Users/ovanni/Library/Containers/com.docker.docker/Data
Oct 11 21:58:12 MacBook-Pro-di-ovanni Docker[com.docker.vmnetd][6727] <Critical>: File /var/run/docker.sock is a symlink or a socket
Oct 11 21:58:12 MacBook-Pro-di-ovanni Docker[com.docker.vmnetd][6727] <Notice>: Symlinking /var/run/docker.sock to /Users/ovanni/Library/Containers/com.docker.docker/Data/s60
Oct 11 21:58:12 MacBook-Pro-di-ovanni Docker[com.docker.docker][6704] <Error>: Symlinks are not correctly installed.
Oct 11 21:58:12 MacBook-Pro-di-ovanni Docker[com.docker.docker][6704] <Notice>: NSUserDefaults.synchronise() returned false
Oct 11 21:58:12 MacBook-Pro-di-ovanni Docker[com.docker.docker][6704] <Notice>: com.docker.osx.hyperkit.linux launched with PID 6730
Oct 11 21:58:12 MacBook-Pro-di-ovanni Docker[com.docker.osx.hyperkit.linux][6730] <Notice>: Acquired task manager lock
Oct 11 21:58:12 MacBook-Pro-di-ovanni Docker[com.docker.osx.hyperkit.linux][6730] <Notice>: Maximum number of file descriptors is 10240

@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 20, 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

3 participants