After I update my Docker version to 0.8.0
, I get an error message while entering sudo docker version
:
Client version: 0.8.0
Go version (client): go1.2
Git commit (client): cc3a8c8
2014/02/19 12:54:16 Can't connect to docker daemon. Is 'docker -d' running on this host?
And I've followed the instructions and entered command sudo docker -d
, and I got this:
[/var/lib/docker|2462000b] +job initserver()
[/var/lib/docker|2462000b.initserver()] Creating server
open /var/lib/docker/aufs/layers/cf2414da53f9bcfaa48bc3d58360d7f1cfd3784e4fe51fbef95197709dfc285d: no such file or directory[/var/lib/docker|2462000b] -job initserver() = ERR (1)
2014/02/19 12:55:57 initserver: open /var/lib/docker/aufs/layers/cf2414da53f9bcfaa48bc3d58360d7f1cfd3784e4fe51fbef95197709dfc285d: no such file or directory
How do I solve the problem?
If regenerating TLS certificates doesn't work
Try restarting the docker machine and setting the env variable:
Check if the machine is running with:
or alternatively
This worked for me. However, if you still don't have the daemon up, Docker's troubleshooting page details a process for stopping, removing and creating a new machine.
Try adding the current user to
docker
group:Then log out and login.
Have you tried turning it off and on again? :-)
I had the same issue after upgrading to Docker 1.10.1 on my Mac. I did the following:
On the Docker Quickstart Terminal
then
then restarted Docker Quickstart Terminal
This solved my problem.
I have the same error and trying
docker-machine regenerate-certs
oreval..
did not work for me.This on OS X 10.11.3 (El Capitan) and Docker v1.10.1. I was able to fix it only by deleting and recreating docker-machine again. Source
If running
docker-machine ls
, it shows you a similar output to the one below;Try removing your Docker machine with;
Where
default
is your Docker machine name. Then;Creates a new Docker machine.
Double check that everything looks normal now (no errors or unknown Docker) with:
Finally don't forget to run
"$(docker-machine env default)"
before you continue or run the Docker Quickstart Terminal which does it for you...Ok so I started having this problem today. Then I saw a lot of responses but none seem to have worked for me. First most of the instructions where directed to linux. And for the mac version they were all talking about running 'docker-machine'. I assume you use docker-machine if you install docker toolbox because then docker will be running in a virtual machine for windows and mac platforms. But its 2017 now and docker for mac is really stable hence no need for using the toolbox.
Not sure how the daemon stopped though. But to restart it all I had to do was go "Applications" and double click on the docker icon. I was asked to update and Relaunched which I accepted. After that everything worked like a charm.