Docker ps not working [resolved]

Docker Desktop for Mac
1

After upgrading to 10.11.4

Docker ps does not return.

More info:

macbook-pro-de-ludovic:proxy Ludo$ id
uid=501(Ludo) gid=20(staff) groups=20(staff),12(everyone),61(localaccounts),79(_appserverusr),80(admin),81(_appserveradm),98(_lpadmin),501(access_bpf),33(_appstore),100(_lpoperator),204(_developer),395(com.apple.access_ftp),398(com.apple.access_screensharing),399(com.apple.access_ssh)
macbook-pro-de-ludovic:proxy Ludo$ ls -lah /var/run/docker.sock /var/tmp/docker.sock
lrwxr-xr-x 1 root daemon 20B 16 avr 16:06 /var/run/docker.sock -> /var/tmp/docker.sock
srwxr-xr-x 1 Ludo wheel 0B 16 avr 16:06 /var/tmp/docker.sock
macbook-pro-de-ludovic:proxy Ludo$ env | grep DOCKER
macbook-pro-de-ludovic:proxy Ludo$ pinata diagnose
OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.0-beta7
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/Ludo/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/20160416-161306.tar.gz
Most specific failure is: /Users/Ludo/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/console-ring does not exist
Would you like to upload log files? [Y/N]: Y

Your unique id is: 70F20723-FD34-46B8-BCE9-9D1580E3AC29

2 Likes
2

what did you do to resolve this?

3

I am running into the same thing. Any ideas?

4

I went into settings and did a ‘reset to factory default’. Then just
waited. I think some activity happens in the background that you don’t
see. Also don’t hesitate to restart your computer.

1 Like
5

Indeed, doing a ‘Reset to factory default’ resolved the issue and it works again.
Would be nice to know what this actually does, to figure out what the exact issue is here.

@kizbitz

6

I was able to see more of what is happening behind the scenes with the following command,

syslog -w -k Sender Docker