Docker Community Forums

Share and learn in the Docker community.

Docker becomes unresponsive

Adding some date for the same issue id: 1ECF659F-3697-4563-BF14-4B198B438489

Same here

OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.0-beta7
Running diagnostic tests:
Error docker ps: timeout after 10.00s
Thread 6 killed on uncaught exception Misc.Failure
Error docker ps: timeout after 10.00s
[ERROR]   docker-cli       docker ps failed: Misc.Failure
[OK]      docker-cli
[OK]      Moby booted
[OK]      driver.amd64-linux
[OK]      vmnetd
[OK]      osxfs
[OK]      db
[OK]      slirp
[OK]      menubar
[OK]      environment
[OK]      Docker
[OK]      VT-x
Docker logs are being collected into /tmp/20160415-114854.tar.gz
Most specific failure is: docker ps failed: Misc.Failure
Your unique id is: 626FBD70-6865-46B0-9A0E-D9D2902C7245
Please quote this in all correspondence.

Same issue here…

⋊> ~/w/o/c/component-parcel on prajan/entityfw-0.0.9-adoption ⨯ pinata diagnose 11:34:54
OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.0-beta7
Running diagnostic tests:
Error docker ps: timeout after 10.00s
[ERROR] docker-cli docker ps failed: Misc.Failure
[OK] docker-cli
Error docker ps: timeout after 10.00s
Thread 6 killed on uncaught exception Misc.Failure
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160415-113550.tar.gz
Most specific failure is: docker ps failed: Misc.Failure
Would you like to upload log files? [Y/N]: Y

Your unique id is: 1441F068-195B-49A0-8529-3719A09EA23D
Please quote this in all correspondence.

I run into the issue again when lunching a semi-complicated compose stack.

Interestingly when using
screen ~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty and running docker ps inside the VM everything works and all containers are listed as expected.

docker ps on the mac is just timing out.

I looked into random logfiles inside the VM, but couldn’t see anything obvious, except several:
docker kern.err kernel: serial8250: too much work for irq4
in /var/log/messages, which might be related.

I’m having the same issue as @johanneswuerbach.

Output of piñata diagnose -u:

OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.0-beta7
Running diagnostic tests:
Error docker ps: timeout after 10.00s
[ERROR] docker-cli docker ps failed: Misc.Failure
[OK] docker-cli
Error docker ps: timeout after 10.00s
Thread 6 killed on uncaught exception Misc.Failure
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160417-202208.tar.gz
Most specific failure is: docker ps failed: Misc.Failure
Your unique id is: 991A061B-BB93-42F4-B65B-BF01E47A0A3B
Please quote this in all correspondence.

Also this log from com.docker.osx.xhyve.linux.log:
2016-04-17T20:25:06.225132-05 Error - 2016/04/17 20:25:06.224849 forward.go:165: No entry for MAC ae:24:af:67:cf:32 in /var/db/dhcpd_leases

OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.0-beta7
Running diagnostic tests:
Error docker ps: timeout after 10.00s
[ERROR] docker-cli docker ps failed: Misc.Failure
[OK] docker-cli
Error docker ps: timeout after 10.00s
Thread 6 killed on uncaught exception Misc.Failure
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160418-161413.tar.gz
Most specific failure is: docker ps failed: Misc.Failure
Would you like to upload log files? [Y/N]: Y

Your unique id is: D6563D63-890F-4AB2-BB4E-5B56CA954327

Same issue, was trying to get docker.local to resolve again. Steps to cause the issue were:

  1. Disabled VPN compatibility mode in Docker (found in another thread to do this for docker.local to work)
  2. Disconnected/reconnected form wifi and VPN
  3. Quit and restarted Docker via Finder
  4. Created a new shell session in Terminal

Now docker ps, docker images, all hang and pinata diagnose gives:

OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.0-beta7
Running diagnostic tests:
Error docker ps: timeout after 10.00s
[ERROR] docker-cli docker ps failed: Misc.Failure
[OK] docker-cli
[OK] Moby booted
Error docker ps: timeout after 10.00s
Thread 6 killed on uncaught exception Misc.Failure
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Error exec: nc -U /tmp/diagnose.socket > /tmp/20160419-121925/diagnostics.tar: exit 1
Docker logs are being collected into /tmp/20160419-121925.tar.gz
Most specific failure is: docker ps failed: Misc.Failure
Would you like to upload log files? [Y/N]: y

Your unique id is: 26C29A4D-2A36-4867-9318-FEFF5088739B
Please quote this in all correspondence.

UPDATE:
Rebooted my Macbook and the error persists. Same pinata diagnose output as above.

I was able to resolve this by clicking “Reset to factory defaults” in the Docker Settings menu and letting it reinstall everything.

Same error for me with

serial8250: too much work for irq4

when doing some dmesg inside the screen of docker tty.

OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.0-beta7
Running diagnostic tests:
Error docker ps: timeout after 10.00s
[ERROR]   docker-cli       docker ps failed: Misc.Failure
Error docker ps: timeout after 10.00s
Thread 6 killed on uncaught exception Misc.Failure
[OK]      docker-cli
[OK]      Moby booted
[OK]      driver.amd64-linux
[OK]      vmnetd
[OK]      osxfs
[OK]      db
[OK]      slirp
[OK]      menubar
[OK]      environment
[OK]      Docker
[OK]      VT-x
Docker logs are being collected into /tmp/20160420-152451.tar.gz
Most specific failure is: docker ps failed: Misc.Failure
Would you like to upload log files? [Y/N]: Y

I am getting the same issue. I was able to screen into the Linux VM and docker is working perfect in side of there, but I was not able to ping outside of the VM. I am also not able to ping docker.local from the native OS.

here is the bridge when I do ifconfig:
bridge100: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=3<RXCSUM,TXCSUM>
ether 6a:5b:35:7b:ce:64
inet 192.168.64.1 netmask 0xffffff00 broadcast 192.168.64.255
Configuration:
id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
ipfilter disabled flags 0x2
member: en5 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 12 priority 0 path cost 0
nd6 options=1
media: autoselect
status: active

OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.0-beta7
Running diagnostic tests:
Error docker ps: timeout after 10.00s
[ERROR] docker-cli docker ps failed: Misc.Failure
Error docker ps: timeout after 10.00s
Thread 6 killed on uncaught exception Misc.Failure
[OK] docker-cli
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160420-072731.tar.gz
Most specific failure is: docker ps failed: Misc.Failure
Your unique id is: 6DE31F20-4B71-4F3E-A62B-7B96CD7EBAAF
Please quote this in all correspondence.

I just tried clicking on enabling the VPN button and now it is working. I am not on a VPN, so I really don’t know why I would need to click on this.

I’ve been having the same problem - hangs when running docker - running pinata set network hostnet (vpn compatibility mode) fixed the issue… for now at least. I’m not running a vpn

Any updates on this issue? I am having the same problems here.

$ pinata diagnose
OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.0-beta7
Running diagnostic tests:
Error docker ps: timeout after 10.00s
Thread 6 killed on uncaught exception Misc.Failure
Error docker ps: timeout after 10.00s
[ERROR] docker-cli docker ps failed: Misc.Failure
[OK] docker-cli
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160420-133158.tar.gz
Most specific failure is: docker ps failed: Misc.Failure
Would you like to upload log files? [Y/N]: Y

Your unique id is: 228F994F-FA92-4C35-A4E3-8FF46154C3C3
Please quote this in all correspondence.

screen ~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty and running docker ps


Welcome to Moby alpha
Kernel 4.4.6 on an x86_64 (/dev/ttyS0)

                        ##         .
                  ## ## ##        ==
               ## ## ## ## ##    ===
           /"""""""""""""""""___/ ===
      ~~~ {~~ ~~~~ ~~~ ~~~~ ~~~ ~ /  ===- ~~~
           \______ o           __/
             \    \         __/
              \____\_______/

docker login: root
Welcome to the Moby alpha, based on Alpine Linux.
docker:~# docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
docker:~#
1 Like

Thanks! This fixed it for me too.

With the update today, I don’t see this problem anymore.

1 Like

Yeah I totally forgot to post my findings, but thankfully it was fixed a few weeks ago. the vm was using all of avail addresses allocated by the internal dhcp server. Each time I turned on the app it would increment it’s internal ip up until I noticed it was past the end of avail ip spaces. I think the beta after that one just stopped running it as an internal space and I also ike how it’s connected with localhost better now

Also seem to be solved for me :clap:

This is still happening for me.

95B66FC7-0D06-4F81-AF62-8DC9385BE30C

Still happening for me as well on rc2-beta16, after ~3 days.

D3522133-6F07-4B83-BD85-051C75885B67

try going into preferences and click on Uninstall / Reset, then reset to factory defaults. This fixed the problem for me.