Closed globalcitizen closed 7 years ago
I suspect that you have docker_machine
env left in your .bash_profile
, can you run /Applications/Docker.app/Contents/Resources/bin/docker-diagnose
in your terminal?
Remove any DOCKER_*
env and tell him if it fixed the problem.
Cheers.
I found an ancient cruft-ridden declare -x DOCKER_HOST="tcp://192.168.59.103:2375"
in ~/.profile
.
In the event that failures are thrown, it would really help to improve ease of debugging (and therefore reduce the number of issues submitted) if a message like Cannot connect to the Docker daemon. Is the docker daemon running on this host?
was better written.
Example: Cannot connect to the Docker daemon. Is the docker daemon running on 192.168.69.103:2375? (value from DOCKER_HOST environment variable)
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
Expected behavior
docker ps
lists containers, anddocker pull gentoo/stage3-amd64-hardened:latest
pulls a container.Actual behavior
Information
~/.docker/
to something else, but it made no difference.Other
Diagnostic ID: 3BE80BB2-B4F8-44EA-90D7-00FEA7048FDD
Output of
ps aux |grep -i docker
...