Docker ps and other commands goes in timeout but diagnostic seems ok

Expected behavior

Docker works

Actual behavior

Any command gives timeout


Diagnose id B6A0592F-B712-41C2-A87B-CCCEF5814A98

Steps to reproduce the behavior

  1. run docker ps
1 Like

I’m seeing similar behavior. During the normal course of work the docker-cli becomes totally unresponsive and the only way I’ve found to fix it is to quit/restart docker for mac.

Diagnosis ID: 2C868AAB-A4E1-400C-9EDC-A7EEA139DD24

The error text is as follows:
ERROR: An HTTP request took too long to complete. Retry with --verbose to obtain debug information. If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).

It’s important to note that this error seems to occur at random, or at least I’ve not been able to easily replicated it by doing x, y, then z.

In my case i’ve to completely reset docker VM to factory settings, it’s very annoying…

I’m in the same place - it appears to work with a hard Docker restart.

Diagnosis ID: 44176CDF-54E3-4C10-B378-026A0D33497F

I’ve had the same problems.


Yesterday I was also getting “Bad response from docker daemon” and I had to just run diagnostics and it worked

Docker doesn’t work any more locally, diagnosis ID:

Version 1.12.0-rc3-beta18 (build: 9996)


From Konsole:
12.07.16 10:00:34,958 Docker[31072]: dockerState = Starting
12.07.16 10:01:30,357 Docker[31089]: failed to establish 9P connection: Caught EOF on underlying FLOW
12.07.16 10:01:30,368 Docker[32920]: EOF reading packet from Unix domain socket: closing
12.07.16 10:01:30,368 Docker[32920]: Failed to read hello from client

Again errors on beta18-3-gec40b14


Can we at least know if someone reads these posts and checks for diagnostics?