Docker Daemon often stops responding

[jamestenglish]

Expected behavior

Running docker ps in PowerShell should return the state of the running containers

Actual behavior

Intermittently
docker ps starts returning:

Error response from daemon: Bad response from Docker engine

After this point the daemon is unreachable

The Docker settings window still shows Docker as running:

Information

• Diagnostic ID: EF9888B1-18C0-4038-872D-796EC16BF93C/2017-07-21_08-24-36
• Windows 10 Enterprise, version 1703, build 15063.483
• Docker version 17.06.0-ce-win19 (12801)

Steps to reproduce the behavior

I am unable to reliably reproduce the behavior but this has been happening to me several times a day for the past few days. The only temporary remedy is to restart docker.

[gorbunovav]

this happens for us too on several computers, on both stable and edge versions

[jasonbivins]

Hi @jamestenglish @gorbunovav
Can you check the power management setting on your NIC for me, and disable it if active?
This is a longshot, but I've seen this setting do the weirdest things to programs, especially ones that are as network dependent as Docker.

[jamestenglish]

@jasonbivins I tried that and am still seeing issues.

I think it may have to do with the resource allocation for the MobyVM. When I did a "Reset to factory defaults" things worked fine for several days. However I have containers that need more than the 2GB and CPU.

I have 12 cores and 16GB ram, when I bump the MobyVM Resources up to like 10 CPUs and 12GB I get docker daemon failures often. I've moved it down to 4 CPU and 6GB ram and the failures still happen but are much less frequent - about once a day rather than once an hour.

Is there some gotcha or limit w/ Hyper-V and the MobyVM I am running into w/ expanded resource allocation?

This may be a duplicate of #1028.

See my comment at #1028 (comment).

[docker-robott]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked