Docker Community Forums

Share and learn in the Docker community.

Docker is not responding: console-ring doesn't exist


(Lox99) #1

Expected behavior

Actual behavior

After upgrade to latest beta, docker doesn’t seem to start.

Information

OS X: version 10.11.3 (build: 15D21)
Docker.app: version v1.11.0-beta8.2
Running diagnostic tests:
Error docker ps: timeout after 10.00s
[ERROR]   docker-cli       docker ps failed: Misc.Failure
[OK]      docker-cli
Error docker ps: timeout after 10.00s
Thread 6 killed on uncaught exception Misc.Failure
[ERROR]   Moby booted      /Users/lachlan/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/console-ring does not exist
[OK]      Moby booted
[OK]      driver.amd64-linux
[OK]      vmnetd
[OK]      osxfs
[OK]      db
[OK]      slirp
[OK]      menubar
[OK]      environment
[OK]      Docker
[OK]      VT-x
Error exec: echo "00000003.0000f3a6" | nc -U /var/tmp/com.docker.vsock/connect > /tmp/20160422-124050/diagnostics.tar: exit 1
Docker logs are being collected into /tmp/20160422-124050.tar.gz
Most specific failure is: /Users/lachlan/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/console-ring does not exist
Your unique id is: 82A2A35C-344C-49C2-8AA4-043D63B4B299
Please quote this in all correspondence.

(Lox99) #2

A reboot appears to have fixed this.


(Junzheng) #3

I had the same issue.
$ pinata diagnose -u
OS X: version 10.11.5 (build: 15F34)
Docker.app: version: v1.11.1-beta14.5.m
Running diagnostic tests:
Error docker ps: timeout after 10.00s
[ERROR] docker-cli docker ps failed: Failure(“docker ps: timeout after 10.00s”)
[OK] docker-cli
[ERROR] Moby booted /Users/junzheng/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/console-ring does not exist
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Error docker ps: got timeout (docker ps: exit 1)
Docker logs are being collected into /tmp/20160607-160019.tar.gz
Most specific failure is: /Users/junzheng/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/console-ring does not exist
Your unique id is: 87D27403-E320-46A0-A858-867A1AC955AD
Please quote this in all correspondence.


(Junzheng) #4

Reboot didn’t help. Uninstalled docker mac, and installed it again. I am still getting the same issue.


(Rbkcapdm) #5

I’m getting exactly the same problem with the same OS X and Docker.app versions as junzheng just reported.

This has been the case for the last 2 Docker.app updates.


(Rbkcapdm) #6

FYI, I still had build version 8193 in my Trash folder. It still starts up okay.

Build versions 8623 and the current 8670 do not.


(Gabrielarrillaga) #7

Same problem for me just started today after updating to beta14.5. Restart didn’t help. Diagnostic ID: C84EEAD4-4477-4833-B334-6A86343B4D7F. Reverted to beta13.1.


(Crashdump) #8

A temporary workaround is to delete Docker’s Library folder and restart Docker:
$ rm -rf ~/Library/Containers/com.docker.docker

Be careful as this will also totally WIPE all your local containers/images.


(Jonatin) #9

I think that wiping the directory only fixes the issue because it reset the network back to hostnet. I can reliably reproduce this simply by setting network to nat mode. Changing back to hostnet fixes the issue for me without wiping or resetting anything.


(Tnrich) #10

Hey janatin, can you give a quick step by step for how to change between nat mode and hostnet?

Thanks!