Docker Community Forums

Share and learn in the Docker community.

Docker is unresponsive and eats 200% cpu after macbook wakeup


(Dmitry Kabak) #1

Actual behavior

After macbook wakeup docker process com.docker.hyperkit eats 200% of the cpu, and all the docker commands hang.

This wasn’t noticed before the sleep, and no containers were running in docker.

Information

pinata logs:

OS X: version 10.10.5 (build: 14F1808)
Docker.app: version v1.11.1-beta12
Running diagnostic tests:
[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 /Users/kabbi/Library/Containers/com.docker.docker/Data/@connect > /tmp/20160521-101002/diagnostics.tar: timeout after 30.00s
Docker logs are being collected into /tmp/20160521-101002.tar.gz
Most specific failure is: No error was detected
Your unique id is: E2BDF21B-497B-4BC3-A668-E351EC61C4E5
Please quote this in all correspondence.

docker logs:

5/21/16 9:41:19.026 AM Docker[8429]: System wants to wake up
5/21/16 9:41:19.026 AM Docker[8429]: Asking com.docker.hyperkit to thaw vcpus
5/21/16 9:41:19.027 AM Docker[8429]: vcpu 1 received signal, resuming
5/21/16 9:41:19.033 AM Docker[8429]: vcpu 0 received signal, resuming
5/21/16 10:10:02.920 AM Docker[8427]: server loop caught Failure("Caught EOF on underlying FLOW"): no further requests will be processed
5/21/16 10:10:02.920 AM Docker[20082]: EOF reading packet from Unix domain socket: closing
5/21/16 10:10:02.921 AM Docker[20082]: Failed to read hello from client


Steps to reproduce the behavior

Unfortunately, I wasn’t able to reproduce. After restarting docker twice everything was back to normal.


(Alexandre) #2

This might be cause by a known issue with Docker for Mac (#1224).

Have a look at the following thread and add you diagnostic information to it (if relevant) in order to help the Docker staff: