Docker Community Forums

Share and learn in the Docker community.

Docker beta for Mac hanging on ps

beta

(Alexandre González) #1

Expected behavior

  1. Write docker ps in a console
  2. Get a list of machines running or an empty list

Actual behavior

It just hangs without any output

Information

$ pinata diagnose -u
OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.0-beta8.2
Running diagnostic tests:
Error docker ps: timeout after 10.00s
Thread 6 killed on uncaught exception Misc.Failure
Error docker ps: timeout after 10.00s
[ERROR]   docker-cli       docker ps failed: Misc.Failure
[OK]      docker-cli
[ERROR]   Moby booted      /Users/alex/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
Docker logs are being collected into /tmp/20160422-110430.tar.gz
Most specific failure is: /Users/alex/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/console-ring does not exist
Your unique id is: E2B1B0A5-675E-43A7-BC88-B106F18A4290
Please quote this in all correspondence.

Steps to reproduce the behavior

I had docker toolbox installed on this machine and everything was working fine:

  1. Download the beta
  2. Install it
  3. Go to a console and write docker ps

(Laurent Gaches) #2

After running a container I can’t run properly docker ps .

Log : Docker[2930] : No entry for MAC 5a:b6:3a:33:cf:32 in /var/db/dhcpd_leases

$ pinata diagnose -u
OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.0-beta8.2
Running diagnostic tests:
Error docker ps: timeout after 10.00s
Thread 6 killed on uncaught exception Misc.Failure
Error docker ps: timeout after 10.00s
[ERROR] docker-cli docker ps failed: Misc.Failure
[OK] docker-cli
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160422-113742.tar.gz
Most specific failure is: docker ps failed: Misc.Failure
Your unique id is: 41A0E730-3D4C-4147-8243-5074A5734A55
Please quote this in all correspondence.


(Mattmcclean) #3

I am facing the same issue. Output of pinata command is the following:

$ pinata diagnose -u
OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.0-beta8.2
Running diagnostic tests:
Error docker ps: timeout after 10.00s
Thread 6 killed on uncaught exception Misc.Failure
Error docker ps: timeout after 10.00s
[ERROR]   docker-cli       docker ps failed: Misc.Failure
[OK]      docker-cli
[OK]      Moby booted
[OK]      driver.amd64-linux
[OK]      vmnetd
[OK]      osxfs
[OK]      db
[OK]      slirp
[OK]      menubar
[OK]      environment
[OK]      Docker
[OK]      VT-x
Docker logs are being collected into /tmp/20160422-111421.tar.gz
Most specific failure is: docker ps failed: Misc.Failure
Your unique id is: AEE09F15-554C-4934-8950-967ACF18CAEE
Please quote this in all correspondence.

(boB Rudis) #4

Same…

$ pinata diagnose -u
OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.0-beta8.2
Running diagnostic tests:
[ERROR]   docker-cli       Connection refused (ECONNREFUSED) connecting to /var/run/docker.sock: check if service is running
[ERROR]   docker-cli       Connection refused (ECONNREFUSED) connecting to /var/tmp/docker.sock: check if service is running
Error docker ps: timeout after 10.00s
[ERROR]   docker-cli       docker ps failed: Misc.Failure
[OK]      docker-cli
[OK]      Moby booted
[ERROR]   driver.amd64-linux Connection refused (ECONNREFUSED) connecting to /tmp/u.socket: check if service is running
[ERROR]   driver.amd64-linux Docker.app/Contents/MacOS/com.docker.driver.amd64-linux -db is not running
[OK]      driver.amd64-linux
[OK]      vmnetd
[ERROR]   osxfs            com.docker.osxfs is not running
[OK]      osxfs
[ERROR]   db               Connection refused (ECONNREFUSED) connecting to /var/tmp/com.docker.db.socket: check if service is running
[ERROR]   db               com.docker.db is not running
[OK]      db
[ERROR]   slirp            Connection refused (ECONNREFUSED) connecting to /var/tmp/com.docker.port.socket: check if service is running
[ERROR]   slirp            com.docker.slirp is not running
[OK]      slirp
[OK]      menubar
[OK]      environment
[OK]      Docker
[OK]      VT-x
Error docker ps: got timeout (docker ps: exit 1)
Thread 6 killed on uncaught exception Misc.Failure
Error exec: echo "00000003.0000f3a6" | nc -U /var/tmp/com.docker.vsock/connect > /tmp/20160426-202930/diagnostics.tar: exit 1
Docker logs are being collected into /tmp/20160426-202930.tar.gz
Most specific failure is: com.docker.slirp is not running
Your unique id is: AA4A1527-BEA6-41BE-BDDF-5F31C4568BEC
Please quote this in all correspondence.

(Willisrocks) #5

Same here as well.

~|⇒ pinata diagnose -u
OS X: version 10.11.4 (build: 15E65)
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]   Moby booted      /Users/chris/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/console-ring does not exist
[OK]      Moby booted
[ERROR]   driver.amd64-linux Connection refused (ECONNREFUSED) connecting to /tmp/u.socket: check if service is running
[ERROR]   driver.amd64-linux Docker.app/Contents/MacOS/com.docker.driver.amd64-linux -db is not running
[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)
Thread 6 killed on uncaught exception Misc.Failure
Docker logs are being collected into /tmp/20160426-180425.tar.gz
Most specific failure is: Docker.app/Contents/MacOS/com.docker.driver.amd64-linux -db is not running
Your unique id is: 5CA84152-6B74-4621-94CB-66CCCBA76EB1
Please quote this in all correspondence.

(Cridenour) #6

I had this but a full system restart fixed it for me.


(Thibaud Lepretre) #7

Full system restart is not enough for me. I have to uninstall & reinstall docker for mac


(Daniel Whatmuff) #8

For anyone who switched from Docker Machine to Docker Beta, you need to unset environment variables first:

$ unset DOCKER_HOST DOCKER_MACHINE_NAME DOCKER_TLS_VERIFY DOCKER_CERT_PATH

(Daniel Demmel) #9

Restarting or unsetting env variables didn’t help for me, but doing a pinata restart as advised in this thread did: Restart Docker from command line


(Daniel Demmel) #10

Well, ps started to work, but actually starting containers don’t :frowning:

Error response from daemon: pool configuration failed because of Key not found in store


(Amanly) #11

Full system restart, nor unsetting env variables not pinata worked for me.

Alexs-MBP-5:demo alex$ unset DOCKER_HOST DOCKER_MACHINE_NAME DOCKER_TLS_VERIFY DOCKER_CERT_PATH
Alexs-MBP-5:demo alex$ pinata restart
Alexs-MBP-5:demo alex$ pinata diagnose -u
OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.0-beta9
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
[OK]      Moby booted
[OK]      driver.amd64-linux
[OK]      vmnetd
[OK]      osxfs
[OK]      db
[OK]      slirp
[OK]      menubar
[OK]      environment
[OK]      Docker
[OK]      VT-x
Docker logs are being collected into /tmp/20160430-191007.tar.gz
Most specific failure is: docker ps failed: Misc.Failure
Your unique id is: 08517BC0-42FF-437F-B24F-6CDFF4DBCD95
Please quote this in all correspondence.
Alexs-MBP-5:demo alex$ docker ps```

(Amanly) #12

Going to Settings… and then clicking Reset to factory defaults worked for me.


(Adamgotterer) #13

Happened for me after a docker cp command seemed to have stalled after waiting a long while. After killing the hung copy command the docker cli become unresponsive.

OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.1-beta10
Running diagnostic tests:
Error docker ps: timeout after 10.00s
Thread 6 killed on uncaught exception Misc.Failure
Error docker ps: timeout after 10.00s
[ERROR] docker-cli docker ps failed: Misc.Failure
[OK] docker-cli
[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 echo “00000003.0000f3a6” | nc -U /var/tmp/com.docker.vsock/connect > /tmp/20160504-184917/diagnostics.tar: timeout after 30.00s
Docker logs are being collected into /tmp/20160504-184917.tar.gz
Most specific failure is: docker ps failed: Misc.Failure
Your unique id is: AA785D1E-F90A-40E9-BFAB-97813C2C7161
Please quote this in all correspondence.


(Michael Murray) #14

This has been happening to me pretty often, about once daily.
A full system reboot usually fixes it, but is there any way to restart the VM without doing a full system reboot or resetting to factory defaults? “pinata restart” just exits immediately and seemingly does nothing.

$ pinata diagnose -u
OS X: version 10.11.3 (build: 15D21)
Docker.app: version v1.11.1-beta10
Running diagnostic tests:
Error docker ps: timeout after 10.00s
Thread 6 killed on uncaught exception Misc.Failure
Error docker ps: timeout after 10.00s
[ERROR] docker-cli docker ps failed: Misc.Failure
[OK] docker-cli
[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 echo “00000003.0000f3a6” | nc -U /var/tmp/com.docker.vsock/connect > /tmp/20160504-190214/diagnostics.tar: timeout after 30.00s
Docker logs are being collected into /tmp/20160504-190214.tar.gz
Most specific failure is: docker ps failed: Misc.Failure
Your unique id is: 94B87879-B425-4C50-83C1-1053C7186EB4
Please quote this in all correspondence.


(Nauraushaun) #15

I’m with you. I’ve been right-clicking the Docker icon in the toolbar at the top, going to Quit Docker, then restarting via the Spotlight shortcut.

Works every time, but is inconvenient. It’s about once a day for me too.
Also it’s not just ps. ps hangs because the whole Docker VM has hung - ps is usually just the first place you see it. The canary if you will.


(Abuchanan) #16

Having the same issue.

❯ pinata diagnose -u [11:04:48]
OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.1-beta11
Running diagnostic tests:
Error docker ps: timeout after 10.00s
Thread 6 killed on uncaught exception Misc.Failure
Error docker ps: timeout after 10.00s
[ERROR] docker-cli docker ps failed: Misc.Failure
[OK] docker-cli
[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/20160512-110448/diagnostics.tar: exit 1
Docker logs are being collected into /tmp/20160512-110448.tar.gz
Most specific failure is: docker ps failed: Misc.Failure
Your unique id is: 9EBDEB16-8652-4944-8BC5-0838E506C9AC
Please quote this in all correspondence.


(Patrickwebs) #17

I did a factory reset and seems to have fixed the issue. Neither pinata restart nor restarting my mac fixed it. Before fixing it, I saw:

~/ pinata diagnose -u OS X: version 10.10.5 (build: 14F1713) Docker.app: version v1.11.1-beta11 Running diagnostic tests: Error docker ps: timeout after 10.00s [ERROR] docker-cli docker ps failed: Misc.Failure [OK] docker-cli [OK] Moby booted Error docker ps: timeout after 10.00s Thread 6 killed on uncaught exception Misc.Failure [OK] driver.amd64-linux [OK] vmnetd [OK] osxfs [OK] db [OK] slirp [OK] menubar [OK] environment [OK] Docker [OK] VT-x Docker logs are being collected into /tmp/20160512-160218.tar.gz Most specific failure is: docker ps failed: Misc.Failure Your unique id is: DAB18839-2998-4C8B-9097-69741B1C404F Please quote this in all correspondence.


(Scharfat) #18

I was seeing similar issues and the only thing that fixed it was the factory reset in settings. I’m seeing this issue very frequently as others have stated. It seems to be related to when my computer goes to sleep instead of shutting down.


(Joseym) #19

This worked for me as well


(Stewart) #20

Hi @scharfat,

It looks like you have the same problem that I mentioned here: Running containers die when machine suspended