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

Cannot connect to daemon on fresh install: Cannot connect to the Docker daemon at tcp://192.168.59.103:2376. Is the docker daemon running? #1386

Closed
jaredonline opened this Issue Mar 4, 2017 · 4 comments

Comments

Projects
None yet
3 participants
@jaredonline

Expected behavior

docker run hello-world runs the hello world app and works immediately after installing docer.

Actual behavior

$ docker run hello-world
docker: Cannot connect to the Docker daemon at tcp://192.168.59.103:2376. Is the docker daemon running?.
See 'docker run --help'

Information

Output of diagnostics:

Docker for Mac: version: 17.03.0-ce-mac1 (e5a07a1a6)
macOS: version 10.10.5 (build: 14F2109)
logs: /tmp/7F4A8A8E-8CC9-4E9B-B357-E48062E96875/20170304-125817.tar.gz
[OK]     vmnetd
[OK]     dns
[OK]     driver.amd64-linux
[OK]     virtualization VT-X
[OK]     app
[OK]     moby
[OK]     system
[OK]     moby-syslog
[OK]     db
[OK]     env
[OK]     virtualization kern.hv_support
[OK]     slirp
[OK]     osxfs
[OK]     moby-console
[OK]     logs
[OK]     docker-cli
[OK]     menubar
[OK]     disk

Diagnostic ID:

7F4A8A8E-8CC9-4E9B-B357-E48062E96875

Steps to reproduce the behavior

  1. Install Docker for Mac on OS X Yosemite 10.10.5
  2. Open iTerm 2
  3. Run docker run hello-world
@jaredonline

This comment has been minimized.

Show comment
Hide comment
@jaredonline

jaredonline Mar 4, 2017

FWIW, I'm also experiencing #1385 as well (I plus-oned it there).

FWIW, I'm also experiencing #1385 as well (I plus-oned it there).

@jessethegame

This comment has been minimized.

Show comment
Hide comment
@jessethegame

jessethegame Mar 5, 2017

I had the same issue today

I had used boot2docker in the past and found out it was deprecated, so I installed docker for mac and upgraded OSX to 10.10.5

It turned out that the old configuration in my ~/.bashrc had a few DOCKER_ env vars, one of which DOCKER_HOST=tcp://192.168.59.103:2376.

Removing the env vars from my .bashrc solved the problem for me.

I had the same issue today

I had used boot2docker in the past and found out it was deprecated, so I installed docker for mac and upgraded OSX to 10.10.5

It turned out that the old configuration in my ~/.bashrc had a few DOCKER_ env vars, one of which DOCKER_HOST=tcp://192.168.59.103:2376.

Removing the env vars from my .bashrc solved the problem for me.

@MagnusS

This comment has been minimized.

Show comment
Hide comment
@MagnusS

MagnusS Mar 8, 2017

Member

Thanks for the report @jaredonline. As @jessethegame mentions above this looks like there are left over DOCKER_ environment variables that are set incorrectly. Removing these should fix the issue.

I'm closing this issue for now, but please let us know if this didn't resolve the issue.

Member

MagnusS commented Mar 8, 2017

Thanks for the report @jaredonline. As @jessethegame mentions above this looks like there are left over DOCKER_ environment variables that are set incorrectly. Removing these should fix the issue.

I'm closing this issue for now, but please let us know if this didn't resolve the issue.

@MagnusS MagnusS closed this Mar 8, 2017

@jaredonline

This comment has been minimized.

Show comment
Hide comment
@jaredonline

jaredonline Mar 8, 2017

Thanks @jessethegame and @MagnusS [= This worked for me =D

Thanks @jessethegame and @MagnusS [= This worked for me =D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment