Docker Community Forums

Share and learn in the Docker community.

After reboot of my MPB docker quit working

(André Schwarzer) #1

Expected behavior

name$ docker ps should list my running or no running container(s)
name$ docker run whatsoever should run a container

Actual behavior

Waiting [] “box” in terminal is the only output I get. Only name$ docker --help works.


MBP i7 2.2GHz
10.11.4 (15E65)

Version 1.11.1-beta10 (build: 6662)

Steps to reproduce the behavior

Not sure.
Post on Twitter

(Dave Tucker) #2

@23r01nf1n17y could you try running pinata diagnose -u and post the output here? That will send us some logs so we can see what’s going on.
Out of interest, does restarting the app clear the problem?

(André Schwarzer) #3

Restarting of the application and the Mac itself doesn’t change a thing.

schwarzer:~ andre$ pinata diagnose -u
OS X: version 10.11.4 (build: 15E65) version v1.11.1-beta10
Running diagnostic tests:
Error docker ps: timeout after 10.00s
[ERROR]   docker-cli       docker ps failed: Misc.Failure
Error docker ps: timeout after 10.00s
Thread 6 killed on uncaught exception 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-135803/diagnostics.tar:     timeout after 30.00s
Docker logs are being collected into /tmp/20160504-135803.tar.gz
Most specific failure is: docker ps failed: Misc.Failure
Your unique id is: 6EFAD6AD-84B9-4BBF-8CD3-B98918D3DC4F
Please quote this in all correspondence.

(Dave Tucker) #4

How about a “Reset to Factory Defaults” from within the menu?

(André Schwarzer) #5

Thanks @davetucker for this hint. It did the trick, but also doesn’t explains what causes this issue. Anyways it works now. :slight_smile: