Docker Community Forums

Share and learn in the Docker community.

Cannot connect to Docker daemon w/ 1.11.1 beta10 (build 6662)


(Kenyee) #1

Expected behavior

“docker info” should give me a list of containers and “docker version” should give me the version of the daemon.
I did try the reset to factory defaults in the Docker app from the status bar at the top of the OSX screen

Actual behavior

$ docker version
Client:
Version: 1.11.1
API version: 1.23
Go version: go1.5.4
Git commit: 5604cbe
Built: Wed Apr 27 00:34:20 2016
OS/Arch: darwin/amd64
Cannot connect to the Docker daemon. Is the docker daemon running on this host?
$ docker info
Cannot connect to the Docker daemon. Is the docker daemon running on this host?

Information

$ pinata diagnose -u
OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.1-beta10
Running diagnostic tests:
Error docker ps: timeout after 10.00s
[ERROR] docker-cli docker ps failed: Misc.Failure
[OK] docker-cli
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[ERROR] environment the variables DOCKER_CERT_PATH DOCKER_TLS_VERIFY DOCKER_MACHINE_NAME DOCKER_HOST should not be set
[OK] Docker
[OK] VT-x
Error docker ps: got timeout (docker ps: exit 1)
Thread 6 killed on uncaught exception Misc.Failure
Docker logs are being collected into /tmp/20160506-130038.tar.gz
Most specific failure is: the variables DOCKER_CERT_PATH DOCKER_TLS_VERIFY DOCKER_MACHINE_NAME DOCKER_HOST should not be set
Your unique id is: EA067E1B-FF79-4907-A884-B7B167FD753C
Please quote this in all correspondence.
OSX 10.11.4 (latest updates as of this date)

Steps to reproduce the behavior

see above


(Kenyee) #2

hmm…I can’t upload attachments…this forum claims I’m a new user :frowning:


(Kenyee) #3

FYI, I unset all the environment variables and it works fine now :slight_smile:
DOCKER_CERT_PATH DOCKER_TLS_VERIFY DOCKER_MACHINE_NAME DOCKER_HOST
all had to be removed. If the new native Docker app no longer needs these, it should make this an error instead of a warning…or explicitly say “can’t connect to host at $DOCKER_HOST…unset it and we’ll connect to your local machine if you’re running native Docker”