An error occurred trying to connect version 1.9.0 #17846
Comments
|
Hi! Please read this important information about creating issues. If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead. If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information. This is an automated, informational response. Thank you. For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues BUG REPORT INFORMATIONUse the commands below to provide key information from your environment:
Provide additional environment details (AWS, VirtualBox, physical, etc.): List the steps to reproduce the issue: Describe the results you received: Describe the results you expected: Provide additional info you think is important: ----------END REPORT --------- #ENEEDMOREINFO |
|
BUG REPORT INFORMATION Use the commands below to provide key information from your environment: docker version: 1.9.0 Provide additional environment details (AWS, VirtualBox, physical, etc.): List the steps to reproduce the issue:
Describe the results you received: An error occurred trying to connect: Get http:///var/run/docker.sock/v1.21/containers/json?all=1: read unix /var/run/docker.sock: connection reset by peer ----------END REPORT --------- |
|
These commands solved my problem: If you want to make progress the following can be used as a workaround:
|
|
I had the same problem. Your solution helped me too. Thank you. |
|
@chiavegatto Thx, it works! |
|
@chiavegatto @kevin125 @kesopeso by any chance you tried docker daemon from the master or RCs before doing the upgrade from 1.8 to 1.9 ? |
|
@chiavegatto @kevin125 @kesopeso Any chance, you have the docker logs during the time this happened. docker apparently panicked and if my guess is correct you hit #17639. If that is case, you can be assured that it will be available in 1.9.1 |
|
I've found that the solution posted by @chiavegatto works for me as well. I can reproduce this problem very easily. The following 3 line dockerfile causes this problem to occur on my system every time I try to build it: FROM ubuntu Here is the output: $ docker build -t test_img . After experiencing this problem, all attempts to interact with the docker daemon fail: $ docker ps $ docker version $ docker info $ uname -a $ dpkg -l | grep docker When building the following output is written to /var/log/syslog: Nov 12 18:24:11 precise-sandbox kernel: [26947.901793] aufs au_opts_verify:1612:docker[30411]: dirperm1 breaks the protection by the permission bits on the lower branch |
|
This problem was happening for me continually but I've been able to resolve it. I tried uninstalling (purging) the docker-engine package and then re-installing it. The problem remained. I tried uninstalling the docker-engine package and then deleting the /var/lib/docker directory (this required a reboot). After re-installing the docker-engine package, everything seems to work as expected. It seems that the docker daemon had some invalid/corrupted data on disk that was preventing it from working correctly. |
|
Thank you, chiavegatto
|
|
Not running for me too, tried every possible solution: Client: uname-a: docker info: |
|
@saurabhnsonar kernel 2.6 is too old to be running docker, and not supported, so docker failing on that is probably expected |
|
@thaJeztah I am getting the same error with docker 1.9.1 on ubuntu 14.04 following a system restart. The workaround works for me but I need to automate it to happen after restart. docker version 1.9.1, build a34a1d5 |
|
@gilo it may be that the daemon didn't shut down clean because of that restart, resulting in some corruption in the database. I think @aboch made changes in libnetwork to better recover from those situations. If you encounter that situation, could you backup the old |
|
@thaJeztah I will try to backup the file on the next encounter. btw, since the workaround here is about deleting it... is it a good practice to remove it at reboot (a cron job)? |
|
@gilo that shouldn't be needed (perhaps as a temporary workaround though), wondering why it would get corrupt on a regular reboot. |
|
@chiavegatto you solve my problem,thanks |
|
thanks @chiavegatto -- that worked for me too on Docker version 1.9.0, build 76d6bc9. I had the problem on ubuntu 14.04 after a clean reboot. |
|
@chiavegatto thank you so much! I just had the same problem and that worked perfectly! |
|
I am also facing the same problem on Docker version 1.9.0 on Ubuntu 14.04. I have some containers that need to be up 24x7 but they stop working at least once a week. @chiavegatto 's workaround solved my problem but it keeps repeating. |
|
I can confirm the @chiavegatto's solution works on Docker version 1.9.1 on Ubuntu 14.04. Thank you. |
|
Thanks @scher200 your solution worked for me on docker 1.9.1 ubuntu 14.04. cheers. |
|
Is anyone still encountering this on docker 1.10? Otherwise I think we should close this |
|
Occurred to me on 1.10.1 build 9e83765: Stopping the daemon, removing |
|
@mlaitinen was that on a fresh 1.10.1 install, or an upgrade from 1.9.x ? |
|
An upgrade from 1.9.x. Unfortunately I don't have any more details because I removed |
|
I have the same problem with ubuntu 14.4 and I have docker 1.12 any advice ho to run it? |
|
Hi Alex, I am also on ubuntu 14.04.3 and Docker 1.12 and my local-kv.db is at: |
|
Hi scher200 and Alex, I have the same problem on ubuntu 14.04.3 and Docker 1.12.
The result of DISTRIB_ID=Ubuntu |
|
I am sorry I can't replicate this now with the exact same version of 2016-08-08 14:17 GMT+02:00 FumiakiKato notifications@github.com:
|
|
Get the same issue on my server. I could provide credentials for someone to debug it if needed. |
|
@scher200 If it helps) I've no I believe the problem that it is on OpenVZ |
|
any update on this? I'm getting this error on v1.12 and CentOS 6 |
|
@carlosmmelo CentOS 6 is not a supported platform for Docker for over a year |
|
yeah maybe, please add your errors, i think you'll help others too 2016-08-10 20:43 GMT+02:00 Alex notifications@github.com:
|
|
I was configured for aufs and was using a new system image, but forgot this step when creating the image: |
|
I've also investigated this issue and it seems it's coming from system using old 2.6.x kernel. |
|
I was able to fix it by running (see kenorb response http://stackoverflow.com/a/34887761/99248) |
|
@raisercostin your solution worked for me on docker 1.12.1. ubuntu 14.04. I run ubuntu 14.04 with VirtalBox and Vagrant . thanks |
|
I'm closing this issue, because this has become a collection of multiple issues (most related to either a corrupted file, or an incomplete installation/upgrade), resulting in the docker daemon being unable to start. (Removing If you run into a similar issue, please check / provide relevant daemon logs as well as those may give more information why the daemon is unable to start, and open a new issue if you suspect there's a bug. |
|
apt-get install linux-image-extra-$(uname -r) |
|
@genggjh Thanks this fixed it for me. Doing: |
|
Docker was working and then after not using for a while, it stopped working and gave me this same issue. I am using Ubuntu 14.04. Removing the local-kb.db file did not fix the issue. FIXED! The issued seems to come from a Kernel upgrade I did(upgraded from 4.4.0 to 4.8.6). Docker worked again rebooting and selecting the previous kernel in GRUB(Kernel 4.4.0) |
|
In my case I had to delete It looks like there are a number of different issues that might be causing the following error message: What makes this difficult to solve is that multiple different problems result in the same error message. There is a better way to troubleshoot. As suggested by @caffeineaddiction in #20221, run the docker daemon manually to be able to view the error messages. You should get an error message which will help you google for a more specific solution (rather than randomly trying all suggested fixes in this thread) I'd already done |
|
In my case, I have ever used the overlay network. so I have a configuration in /etc/default/docker that related to the network card eth1. I have ifdown the eth1 by mistake then I get the same error. After I ifup the network card eth1. All thing is ok. |
|
Launching the daemon from the command line helped a lot. Thanx @mbylstra. Doing: rm -rf /var/run/docker, solved the problem (but I didn't have images yet...) |
|
sorry ,我最后选择了重装docker.... |
|
Had to delete |
|
@chiavegatto Not a suiteable solution for me since all configuration like networks got lost, and I've to restart all containers. But what worked for me: Moving the I have no clue what happens here and why... Using |
|
Hi, my name is Leandro Combinato cd /var/run/ Thank very much! |
谢谢非常管用 |
Execute command:
docker ps -a
Error:
An error occurred trying to connect: Get http:///var/run/docker.sock/v1.21/containers/json?all=1: read unix /var/run/docker.sock: connection reset by peer
I'm using ubuntu and updated version 1.8.3 to 1.9.0.
docker version
Client:
Version: 1.9.0
API version: 1.21
Go version: go1.4.2
Git commit: 76d6bc9
Built: Tue Nov 3 17:43:42 UTC 2015
OS/Arch: linux/amd64
An error occurred trying to connect: Get http:///var/run/docker.sock/v1.21/version: read unix /var/run/docker.sock: connection reset by peer
The text was updated successfully, but these errors were encountered: