-
Notifications
You must be signed in to change notification settings - Fork 594
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
are you trying to connect to a tls-enabled daemon without tls #3
Comments
Can you give a little more info? Are you running boot2docker on a Mac or is this on an ubuntu or other Linux machine? |
Same issue, ubuntu 14.04 |
Fresh Ubuntu 14.04.2, followed instructions from http://docs.docker.com/installation/ubuntulinux/ and got same error message. |
same issue fresh 14.04 |
This sounds like the Docker daemon isn't even starting up. Have you checked the daemon logs? If you're on 14.04, they're probably going to be in |
You need to start the docker daemon |
thanks everyone, let me try |
thanks, |
Restart box if Ubuntu packages have been updated. And "sudo start docker" works !! |
xubuntu user here: I was missing apparmor |
For those using systemd (fedora, centos, redhat, arch, etc...) you should start it running:
If you want it to start automatically you can run:
|
I posted an answer here http://stackoverflow.com/a/30701713/1441295. It may help someone. |
If you are on Ubuntu 15.04 I believe upstart is being replaced by systemd. Someone can correct me on this at this information is way outside my area of expertise. But, in order to start the docker service you will need to take @renatomefidf's advice. Use |
Another possbile reason is that your bios CPU visualization is not enabled. Go and enable it first! |
add sudo service docker start |
after executing $ sudo docker run hello-world that I get this message:
FATA[0000] post http:///var/run/docker.sock/v1.17/containers/create: dial unix /var/run/docker .sock: no such file or directory. are you trying to connect to a TLS-enabled daemon without TLS?
How can I do?? help me
The text was updated successfully, but these errors were encountered: