# Docker becomes unresponsive **URL:** \ **Category:** Docker Desktop\ **Created:** [April 11, 2016, 8:10am UTC](https://forums.docker.com/t/docker-becomes-unresponsive/8853 "2016-04-11T08:10:06Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![johanneswuerbach](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/johanneswuerbach/32/6360_2.png) [@johanneswuerbach](https://forums.docker.com/u/johanneswuerbach)\ **Post date:** [April 11, 2016, 8:10am UTC](https://forums.docker.com/t/docker-becomes-unresponsive/8853/1 "2016-04-11T08:10:07Z")
Shortly after awakening my MacBook from sleep I semi-consistently end up with a not responding docker daemon. ### Information > $ pinata diagnose > OS X: version 10.11.4 (build: 15E65) > Docker.app: version v1.11.0-beta6 > 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 > [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/20160411-100356.tar.gz. > Errors were detected, would you like to upload to bugsnag? [Y/N]: Y > Your unique id in bugsnag is: 575E26AE-18EB-4307-8C46-66C41022E8D9 ### Steps to reproduce the behavior Sadly none, but definitely up for providing more logs when requested. Seems not to be limited to certain Dockerfiles. ---
**Author:** ![joshuarubin](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/joshuarubin/32/6424_2.png) [@joshuarubin](https://forums.docker.com/u/joshuarubin)\ **Post date:** [April 11, 2016, 8:45pm UTC](https://forums.docker.com/t/docker-becomes-unresponsive/8853/2 "2016-04-11T20:45:18Z")
Same problem. > $ pinata diagnose -u > OS X: version 10.11.4 (build: 15E65) > Docker.app: version v1.11.0-beta6 > 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 > [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/20160411-144433.tar.gz. > Your unique id in bugsnag is: 8ED16222-1DF1-488B-9210-11A512EC97AB > Please quote this in all correspondence. ---
**Author:** ![nullpuppy](https://avatars.discourse-cdn.com/v4/letter/n/858c86/32.png) [@nullpuppy](https://forums.docker.com/u/nullpuppy)\ **Post date:** [April 13, 2016, 10:22pm UTC](https://forums.docker.com/t/docker-becomes-unresponsive/8853/3 "2016-04-13T22:22:20Z")
I, too, am getting this now. My system hard-crashed this morning, after reboot, I can’t access Docker for Mac. ```auto $ pinata diagnose -u OS X: version 10.11.4 (build: 15E65) Docker.app: version v1.11.0-beta6 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 [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/20160413-151525.tar.gz. Your unique id in bugsnag is: 97E2FD2D-8791-4CDC-9D63-1DC218E7269E Please quote this in all correspondence. ``` `pinata restart` and `pinata doctor` haven’t done anything and just report everything’s fine, even though it isn’t. ---
**Author:** ![frenchben](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/frenchben/32/5778_2.png) [@frenchben](https://forums.docker.com/u/frenchben)\ **Post date:** [April 14, 2016, 1:21am UTC](https://forums.docker.com/t/docker-becomes-unresponsive/8853/4 "2016-04-14T01:21:11Z")
Thank you for collecting the different logs and uploading them to bugsnag for us. We’ll look through them and see if we can identify what caused the issue. ---
**Author:** ![arangamani](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/arangamani/32/7433_2.png) [@arangamani](https://forums.docker.com/u/arangamani)\ **Post date:** [April 15, 2016, 3:35am UTC](https://forums.docker.com/t/docker-becomes-unresponsive/8853/5 "2016-04-15T03:35:37Z")
I am having the same problem as well `pinata diagnose -u OS X: version 10.11.4 (build: 15E65) Docker.app: version v1.11.0-beta7 Running diagnostic tests: [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/20160414-175218.tar.gz Most specific failure is: No error was detected Your unique id is: 94A30AAD-48B2-477E-962E-040F8D27EF66 Please quote this in all correspondence.` FWIW I was running about 25 containers. This setup works perfectly fine with docker-machine. I am going back to docker-machine for now 😥 ---
**Author:** ![xordoquy](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/xordoquy/32/7593_2.png) [@xordoquy](https://forums.docker.com/u/xordoquy)\ **Post date:** [April 15, 2016, 8:56am UTC](https://forums.docker.com/t/docker-becomes-unresponsive/8853/6 "2016-04-15T08:56:04Z")
Same here: pinata 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 [OK] Moby booted [OK] driver.amd64-linux [OK] vmnetd [OK] osxfs [OK] db [OK] slirp [OK] menubar [ERROR] environment the variables DOCKER\_CERT\_PATH DOCKER\_TLS\_VERIFY DOCKER\_MACHINE\_NAME DOCKER\_HOST should not be set [OK] Docker [OK] VT-x Error docker ps: got timeout (docker ps: exit 1) Thread 6 killed on uncaught exception Misc.Failure Docker logs are being collected into /tmp/20160415-102453.tar.gz Most specific failure is: the variables DOCKER\_CERT\_PATH DOCKER\_TLS\_VERIFY DOCKER\_MACHINE\_NAME DOCKER\_HOST should not be set Your unique id is: 1CD4BAFC-45FF-4F16-8414-F36B79E031D3 Please quote this in all correspondence. ---
**Author:** ![rickardvonessen](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/rickardvonessen/32/6642_2.png) [@rickardvonessen](https://forums.docker.com/u/rickardvonessen)\ **Post date:** [April 15, 2016, 10:06am UTC](https://forums.docker.com/t/docker-becomes-unresponsive/8853/7 "2016-04-15T10:06:38Z")
Adding some date for the same issue id: 1ECF659F-3697-4563-BF14-4B198B438489 ---
**Author:** ![meyskens](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/meyskens/32/7611_2.png) [@meyskens](https://forums.docker.com/u/meyskens)\ **Post date:** [April 15, 2016, 3:24pm UTC](https://forums.docker.com/t/docker-becomes-unresponsive/8853/8 "2016-04-15T15:24:48Z")
Same here ```auto 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. ``` ---
**Author:** ![praveen12bnitt](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/praveen12bnitt/32/7645_2.png) [@praveen12bnitt](https://forums.docker.com/u/praveen12bnitt)\ **Post date:** [April 15, 2016, 3:45pm UTC](https://forums.docker.com/t/docker-becomes-unresponsive/8853/9 "2016-04-15T15:45:17Z")
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. ---
**Author:** ![johanneswuerbach](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/johanneswuerbach/32/6360_2.png) [@johanneswuerbach](https://forums.docker.com/u/johanneswuerbach)\ **Post date:** [April 16, 2016, 5:04pm UTC](https://forums.docker.com/t/docker-becomes-unresponsive/8853/10 "2016-04-16T17:04:08Z")
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. ---
**Author:** ![lcalcote](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/lcalcote/32/20159_2.png) [@lcalcote](https://forums.docker.com/u/lcalcote)\ **Post date:** [April 18, 2016, 1:25am UTC](https://forums.docker.com/t/docker-becomes-unresponsive/8853/11 "2016-04-18T01:25:59Z")
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 ---
**Author:** ![steel](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/steel/32/7879_2.png) [@steel](https://forums.docker.com/u/steel)\ **Post date:** [April 18, 2016, 9:12pm UTC](https://forums.docker.com/t/docker-becomes-unresponsive/8853/12 "2016-04-18T21:12:16Z")
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 ---
**Author:** ![ecliptik](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/ecliptik/32/4838_2.png) [@ecliptik](https://forums.docker.com/u/ecliptik)\ **Post date:** [April 19, 2016, 7:23pm UTC](https://forums.docker.com/t/docker-becomes-unresponsive/8853/13 "2016-04-19T19:23:41Z")
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. ---
**Author:** ![steel](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/steel/32/7879_2.png) [@steel](https://forums.docker.com/u/steel)\ **Post date:** [April 20, 2016, 1:06am UTC](https://forums.docker.com/t/docker-becomes-unresponsive/8853/14 "2016-04-20T01:06:13Z")
I was able to resolve this by clicking “Reset to factory defaults” in the Docker Settings menu and letting it reinstall everything. ---
**Author:** ![shouze](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/shouze/32/4892_2.png) [@shouze](https://forums.docker.com/u/shouze)\ **Post date:** [April 20, 2016, 1:24pm UTC](https://forums.docker.com/t/docker-becomes-unresponsive/8853/15 "2016-04-20T13:24:06Z")
Same error for me with ```auto serial8250: too much work for irq4 ``` when doing some dmesg inside the screen of docker tty. ```auto 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 ``` ---
**Author:** ![dwitherspoon](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/dwitherspoon/32/8075_2.png) [@dwitherspoon](https://forums.docker.com/u/dwitherspoon)\ **Post date:** [April 20, 2016, 1:28pm UTC](https://forums.docker.com/t/docker-becomes-unresponsive/8853/16 "2016-04-20T13:28:16Z")
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\ mtu 1500 options=3\ 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\ 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. ---
**Author:** ![dwitherspoon](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/dwitherspoon/32/8075_2.png) [@dwitherspoon](https://forums.docker.com/u/dwitherspoon)\ **Post date:** [April 20, 2016, 1:30pm UTC](https://forums.docker.com/t/docker-becomes-unresponsive/8853/17 "2016-04-20T13:30:12Z")
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. ---
**Author:** ![rnbwd](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/rnbwd/32/7838_2.png) [@rnbwd](https://forums.docker.com/u/rnbwd)\ **Post date:** [April 20, 2016, 2:48pm UTC](https://forums.docker.com/t/docker-becomes-unresponsive/8853/18 "2016-04-20T14:48:55Z")
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 ---
**Author:** ![v1k0d3n](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/v1k0d3n/32/1676_2.png) [@v1k0d3n](https://forums.docker.com/u/v1k0d3n)\ **Post date:** [April 20, 2016, 5:38pm UTC](https://forums.docker.com/t/docker-becomes-unresponsive/8853/19 "2016-04-20T17:38:29Z")
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. ```auto 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:~# ``` ---
**Author:** ![ntaprippy](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/ntaprippy/32/3100_2.png) [@ntaprippy](https://forums.docker.com/u/ntaprippy)\ **Post date:** [April 23, 2016, 8:49pm UTC](https://forums.docker.com/t/docker-becomes-unresponsive/8853/20 "2016-04-23T20:49:24Z")
Thanks! This fixed it for me too. [Next page](https://forums.docker.com/t/docker-becomes-unresponsive/8853.md?page=2)