Docker: Are you trying to connect to a TLS-enabled daemon without TLS?

Question

On Linux Mint 17.1 x86_64 with kernel 3.13.0-48-generic and OpenSSL version 1.0.1f-1ubuntu2.11; whenever I try to execute any docker command (like docker login or docker run hello-world), I get the following error:

FATA[0000] Get http:///var/run/docker.sock/v1.18/info: dial unix /var/run/docker.sock: no such file or directory. Are you trying to connect to a TLS-enabled daemon without TLS? 

I have made a group called docker using sudo usermod -aG docker username, I have tried running the commands both as root and normally, added $(boot2docker shellinit 2> /dev/null) to ~/.profile as instructed here, restarted my PC and reinstalled OpenSSL.

Any idea what am I missing? Can this be a hardware issue?

Solution 1

You can check if it has started by running the command ps -ef. You can also grep it to docker if you want to reduce the number of results(using | grep docker). If its of not running, execute

sudo service docker start

OR if it still doesn't work then

You can refer this link

docker docs

You can run docker run -d or docker run -d & so that you can use the same terminal or even close it if. It will set the value to true, so your container will run in "detached" mode, in the background.

You can also auto start it when your OS starts using update-rc.d servicename defaults or you can also refer to the links below, where you have to give docker as service name and your defaults.

Some more links to refer - auto start, upstart

These are different ways of doing it.

Solution 2

I deployed docker on CentOS 7, and my friend first helped me check whether the process/service docker is actually running or not. He used the command ps -ef | grep docker. It turned out that the process wasn't running at all. Finally, he started this process by using the command service docker start. In the end, the problem was solved.

Solution 3

Try installing apparmor

sudo apt install apparmor

There are other things to look for in this answer too.

Solution 4

I had this same problem when I tried to follow along some online resource; I was able to resolve this by running docker as the super user, try adding sudo before your docker commands:

sudo docker ps -a

sudo docker run hello-world

Hope it helps.

Solution 5

I faced the same issue when I was creating docker image from Jenkins simply add the user to docker group and then restart docker services and in my case I have to restart Jenkins services

This was the error which I got

http:///var/run/docker.sock/v1.19/build?cgroupparent=&cpuperiod=0&cpuquota=0&cpusetcpus=&cpusetmems=&cpushares=0&dockerfile=Dockerfile&memory=0&memswap=0&rm=1&t=59aec062a8dd8b579ee1b61b299e1d9d340a1340: dial unix /var/run/docker.sock: permission denied. Are you trying to connect to a TLS-enabled daemon without TLS?
FATAL: Failed to build docker image from project Dockerfile
java.lang.RuntimeException: Failed to build docker image from project Dockerfile


Solution: 

[root@Jenkins ssh]# groupadd docker
[root@Jenkins ssh]# gpasswd -a jenkins docker
Adding user jenkins to group docker
[root@Jenkins ssh]# /etc/init.d/docker restart
Stopping docker:                                           [  OK  ]
Starting docker:                                           [  OK  ]
[root@Jenkins ssh]# /etc/init.d/jenkins restart
Shutting down Jenkins                                      [  OK  ]
Starting Jenkins                                           [  OK  ]
[root@Jenkins ssh]#

View more solutions

Comments

[armandfp]

i did a fresh installation on ubuntu 12.04 (after update the kernel) and i don't know why give this error, i solved installing apparmor

[Doug Schmidt]

This answers needs more upvotes. The official Docker install instructions for Ubuntu are missing this step. I've installed Docker now three times into clean Ubuntu systems (once running 12.04 and twice running 14.04). Each time I've spent an hour searching the web, only to stumble back to this SO answer!

[Beccari]

That is exactly the point. Seems to not be a "problem" at all. It is just the docker daemon need to be running in order to work

[lvthillo]

did you use service docker start or sudo service docker start?

[jonincanada]

Or to register it as a service on linux run: #systemctl enable docker.service

[mkcor]

Further install and config instructions for Ubuntu can be found at docs.docker.com/engine/installation/ubuntulinux.

[Avec]

sudo docker [command] solved the problem for me while using Linux.

[Donald Duck]

While this code may answer the question, providing additional context regarding how and/or why it solves the problem would improve the answer's long-term value.

[Eliethesaiyan]

chmod 777 give the all rights(read,write,execute) to all processes,its bad practice to use 777 but it does solve the problem as you said @DonaldDuck

[Pang]

chmod 777? Oh no.