Docker Community Forums

Share and learn in the Docker community.

Docker Unresponsive


(Dave Padovano) #1

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

  1. Run docker with 5 python containers, some using ubuntu OS, some using alpine.
  2. Continue running application that use a fair amount of memory and CPU for about 30 minutes-1hr.
  3. After about an hr… docker will become unresponsive but will not crash
  4. 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.


(Sergiomaurenzi) #2

Hi all,

I’ve had a similar behavior after stressing some containers related to a monitoring application (Dynatrace EasyTravel).

Diagnostic ID: 01157CF6-7689-4564-8F9A-F715F2BA1A58

Docker for Mac: version: mac-v1.12.0-beta20
OS X: version 10.11.5 (build: 15F34)
logs: /tmp/20160726-215937.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

Regards,


(Pcm32) #3

Hi there,

I’m getting the same behaviour, even after a restart and a reset to factory settings (so wiped the VM):

Diagnostic ID: 855D62BD-9A70-4217-9465-D2FC9BAD905A

Docker for Mac: version: mac-v1.12.0-beta20
OS X: version 10.11.5 (build: 14F1909)
logs: /tmp/20160728-112105.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

My activity viewer shows a large and steady CPU usage from com.docker.hyperkit at ~199%, even though no container is running. Have tried restarting the daemon several times, without success.

When I killed that process (com.docker.hyperkit), it seemed to become responsive again (and messages became more benign in the console).

Thanks!
Pablo