Expected behavior
$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
Actual behavior
$ docker ps -a
^C
Information
Diagnostic ID: 67F47251-5B7D-4B6F-A718-158511E1FF7A
Docker for Mac: version: mac-v1.12.0-beta20
OS X: version 10.10.5 (build: 14F1808)
logs: /tmp/20160726-183133.tar.gz
failure: docker ps failed: Failure(“docker ps: timeout after 10.00s”)
[ERROR] docker-cli
docker ps failed
[OK] app
[OK] moby-syslog
[OK] virtualization
[OK] menubar
[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
- Run docker with 5 python containers, some using ubuntu OS, some using alpine.
- Continue running application that use a fair amount of memory and CPU for about 30 minutes-1hr.
- After about an hr… docker will become unresponsive but will not crash
- Restart docker and now docker engine will become unresponsive
$ docker ps -a
Error response from daemon: Bad response from Docker engine
Only way to resolve the issue is to force close com.docker.hyperkit
There are still some instances of the docker hypervisor process causing the CPU to spike … but that is not always happening when docker becomes unresponsive.