This happens every time my Mac goes into sleep for a longer time (It seems fine if it’s just a few minutes): all containers are stopped, and the docker daemon becomes unresponsive. I have to manually restart the docker daemon to get it working again.
Expected behavior
any docker command in the console should work/respond
i.e. docker ps, docker images, …
Actual behavior
All docker commands hang, never return. Have to force-cancel the command.
Information
Diagnose ID: F187DB1C-3DE2-4293-91ED-9CBC9C2CFF28
Docker for Mac: version: mac-v1.11.2-beta15
OS X: version 10.10.5 (build: 14F1808)
logs: /tmp/20160616-073108.tar.gz
failure: No error was detected
[OK] docker-cli
[OK] app
[OK] menubar
[OK] virtualization
[OK] system
[OK] osxfs
[OK] db
[OK] slirp
[OK] moby-console
[OK] logs
[OK] vmnetd
[OK] env
[OK] moby
[OK] driver.amd64-linux
Steps to reproduce the behavior
Start docker for mac beta. Leave it on. Put your Mac to sleep and leave it over night. In the morning you’d have the above behavior.
There seem to be a few issues with sleeping. Issues we didn’t see on ol’ Docker Machine, and which greatly affect my workflow.
It’s driving me to madness
Agreed. I’ve moved away from testing the beta back to docker machine.
I know that a beta is meant for testing and not production, but it’s just not even ready for that. It got to the point that I was spending more time restarting containers than I was actually doing anything productive - and when it dies during a git commit/push…ARGH…corrupted repos are just no fun.
I agree completely. I’m still using the beta because I feel like I have my finger on the pulse. But really, I miss docker machine, it worked great.
Hopefully things get cleared up soon…
