docker not responding

[daxincaopofu]

Expected behavior

Docker ps to list processes

Actual behavior

No console output

Information

Attempted restart, but no change

Diagnostic ID: 9337C522-8470-44F2-8952-CA77984DB3B9
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.10.5 (Build 14F1909)
[ERROR] docker-cli
docker ps failed
[OK] app
[OK] moby-syslog
[OK] disk
[OK] virtualization
[OK] system
[OK] menubar
[OK] osxfs
[OK] db
[OK] slirp
[OK] moby-console
[OK] logs
[OK] vmnetd
[OK] env
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. ...
2. ...

[mihirv0ra]

Please check #370 i was able to get this resolved, by going to Preferences -> Uninstall/Reset -> Reset , note that it cleans up all the containers and images

[daxincaopofu]

I was able to resolve my issue by killing all the docker processes manually (the docker reset doesn't do this by itself) and starting the docker daemon again. This worked without needing a complete reinstall. Other people have suggested this fix as well. But maybe this is a bug for docker reset? I saw that in the case where the docker ps command froze that even on quitting the docker application, there were still some docker processes running (killing them fixed the issue).

[elgreg]

+1 for killing processes instead of a the complete factory reset. I went with:

ps aux | grep docker | grep -v grep | tr -s " " | cut -d " " -f 2 | xargs kill

Though, arguablye pkill docker would work just as well.

[mchiang0610]

merging with #119

[samoht]

Detected symptom of problem 'invariant-violated' in 9337C522-8470-44F2-8952-CA77984DB3B9/20160818-095607.

An invariant within the code of one of the components was not held. Docker needs to be restarted.

May be related to #89

The following log matches:

Aug 12 08:53:14 ch-nb-343.local Docker[com.docker.driver.amd64-linux][75698] <Notice>: VM: 2016-08-12 13:53:16 +0000 UTC daemon.info vsudd: Connection 69 to: 2376 from: 00000000
Aug 12 08:53:14 ch-nb-343.local Docker[com.docker.driver.amd64-linux][75698] <Notice>: VM: 2016-08-12 13:53:16 +0000 UTC daemon.info vsudd: 69 Done. read: 220 written: 147
Aug 12 08:53:20 ch-nb-343.local Docker[com.docker.osxfs][75696] <Notice>: Volume.stop 8967032f04359a067e700766034cfb0e192b86e983d6475d2322c38c41686a34 (paths = [/Users/xcao/Projects/deployment_change_control/])
Aug 12 08:53:20 ch-nb-343.local Docker[com.docker.osxfs][75696] <Error>: WATCH SUBSCRIBER REMOVAL INVARIANT VIOLATED
Aug 12 08:53:20 ch-nb-343.local Docker[com.docker.driver.amd64-linux][75698] <Notice>: VM: 2016-08-12 13:53:23 +0000 UTC daemon.info vsudd: Connection 70 to: 2376 from: 00000000
Aug 12 08:53:20 ch-nb-343.local Docker[com.docker.driver.amd64-linux][75698] <Notice>: VM: 2016-08-12 13:53:23 +0000 UTC kern.info kernel: docker0: port 1(vethba38e52) entered disabled state
Aug 12 08:53:20 ch-nb-343.local Docker[com.docker.driver.amd64-linux][75698] <Notice>: VM: 2016-08-12 13:53:23 +0000 UTC kern.info kernel: veth21a594a: renamed from eth0

/cc @dsheets

[dsheets]

I do not believe that the original issue was caused by the invariant violation that @samoht cites.

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked