Docker failing to start on Windows 10

[drnybble]

I have previously had Docker running successfully on this system. I updated Docker and now it is not working.

I have uninstalled & reinstalled it -- same behaviour it fails to start.

The Error dialog shows:

Docker hv-sock proxy (vsudd) is not reachable
at Docker.Backend.ContainerEngine.Linux.ConnectToVsud(TaskCompletionSource`1 vmId)
at Docker.Backend.ContainerEngine.Linux.DoStart(Settings settings)
at Docker.Backend.ContainerEngine.Linux.Start(Settings settings)
at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass8_0.b__0(Object[] parameters)
at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)

Information

• Diagnostic ID from "Diagnose & Feedback" in the menu.
  Starting Linux containers:
  3428D7CA-D3F3-473E-B804-62823CB673EB/2017-05-26_12-05-50

Starting Windows containers:
3428D7CA-D3F3-473E-B804-62823CB673EB/2017-05-29_15-24-44

I have installed the latest cumulative update for Windows 10 1607.

This is a Windows 10 VM with hardware virtualization enabled (under VMWare).

The Hyper-V VM is showing CPU activity up to the time Docker decides it has failed. Is there an issue running on slow systems?

[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

[rn]

@drnybble you are running Docker for Windows in a Windows 10 VM on VMware. This configuration is not supported (see https://docs.docker.com/docker-for-windows/troubleshoot/#running-docker-for-windows-in-nested-virtualization-scenarios) primarily because we have no control over how you configure your VM, how much resources you allocate to it and what else is happening in on the host system. Closing

[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