-
Notifications
You must be signed in to change notification settings - Fork 118
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
Comments
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:
May be related to The following log matches:
|
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. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Expected behavior
docker info returns info
Actual behavior
bash: docker: command not found
Information
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
The text was updated successfully, but these errors were encountered: