Docker Community Forums

Share and learn in the Docker community.

Cannot manage containers (Are you trying to connect to a TLS-enabled daemon without TLS?)


(Pascal Lindelauf) #1

I have restarted my Ubuntu 14.04 server, but now I cannot reach the services in the following Docker containers anymore:

$ sudo docker ps
CONTAINER ID        IMAGE                              COMMAND                CREATED             STATUS              PORTS                    NAMES
2ddfda3167dd        ugoarangino/atlassian-confluence   "/bin/sh -c '/opt/at   9 months ago        Up 7 days           0.0.0.0:8101->8090/tcp   confluence          
308f1807fffb        ugoarangino/atlassian-jira         "/bin/sh -c '/opt/at   9 months ago        Up 7 days           0.0.0.0:8100->8080/tcp   jira                
ee33f63ec8a8        postgres                           "/docker-entrypoint.   9 months ago        Up 7 days           5432/tcp                 postgres 

First I thought I’d try to restart a container, but when I try to stop it, I get:

$ sudo docker stop 2ddfda3167dd
Post http:///var/run/docker.sock/v1.19/containers/2ddfda3167dd/stop?t=10: EOF. Are you trying to connect to a TLS-enabled daemon without TLS?
Error: failed to stop containers: [2ddfda3167dd]

I get similar errors for docker restart, etc.

Here’s my version info:

$ sudo docker version
Client version: 1.7.0
Client API version: 1.19
Go version (client): go1.4.2
Git commit (client): 0baf609
OS/Arch (client): linux/amd64
Server version: 1.7.0
Server API version: 1.19
Go version (server): go1.4.2
Git commit (server): 0baf609
OS/Arch (server): linux/amd64

I also double checked that Docker is running:

$ sudo start docker
start: Job is already running: docker

Maybe this has something to to with the fact that these containers are set to auto restart upon reboot? Or maybe because I updated all packages on my system, which might have brought in a new Docker version…?

Where do I go from here?


(Pascal Lindelauf) #2

The “EOF” part of the error message did feel like there is something wrong in some script. So I tried reverting form 1.7.0 back to 1.6.2 and… it worked!

So either it’s a bug in 1.7.0 or I should have ran some kind of upgrade script…? Does anyone know?


(Nick) #3

I also had this problem — upgrading from 1.6.2 to 1.7.1 seemed to crash 6 out of 8 running containers, and leave me with containers that were listed as running, but weren’t (no process) and which couldn’t be stopped, restarted or removed.

Restarting Docker or rebooting the machine had no affect.

Nothing special about the containers, apart from restart=always.

Your solution worked for me, downgrading to 1.6.2 (sudo apt-get install lxc-docker-1.6.2 on Ubuntu). Very wary about upgrading again!


(Jualvarez) #4

@mcoms @plindelauf could you remove those broken containers? I still have them lying around.