Problem: I am trying to run docker inside vagrant, my Vagrantfile contains following:-
config.vm.provision \"docker\" do |d|
d.run \"ubuntu\",
i've gotten the same error response. when i checkout the daemon.json file, and i found that
{
"registry-mirrors": ["http://hub-mirror.c.163.com"]
"graph": "/etc/docker/mirror"
}
as you can see, i missed "," so i corrected it so simple. how careless i was!
{
"registry-mirrors": ["http://hub-mirror.c.163.com"],
"graph": "/etc/docker/mirror"
}
sometimes you need check your code carefully
On your ssh server, run:
systemctl start docker
systemctl status docker
Docker will start on the server and have a socket on its respective.
In my case I had to do:
sudo rm /var/run/docker.pid
sudo docker start [my_container]
I faced a similar issue, running the command sudo service docker restart
, followed by restarting the docker image fixed the issue for me
Start docker deamon by systemctl start docker.service
Be sure to run command as superuser
Here is what happened to me and what could be a possible solution for someone else. I'm running on Ubuntu 16.04.
I ultimately purged and reinstalled everything from the docker-ce install. I mean everything. Still not working...
Through my internet wizardry I was able to find an article (I can't recall where, there were so many) mentioning that the file located at:
$ sudo nano /etc/systemd/system/docker.service
Had a -d in the place of the daemon at Execstart. That wasn't the case for me. I had ...daemon -D..., but I did notice that it was pointing to /usr/bin/local/docker. That didn't exist, but what does exist is /usr/bin/docker. In that location you will also find docker-containerd, dockerd, etc...
Anyway, I made the change to the docker.service file--simply dropping /local out of there. Saved. Then:
$ systemctl daemon-reload
$ sudo service docker restart
$ sudo service docker status (should see active (running))
$ sudo docker run hello-world
Success!