Docker fails to start with error: Docker hv-sock proxy (vsudd) is not reachable

[RealGandy]

Expected behavior

Docker should start

Actual behavior

Docker fails to start with error: Docker hv-sock proxy (vsudd) is not reachable

Information

Diagnostic ID: D15420F9-3B32-4CA5-B828-D30A4313B54B/2017-07-05_15-10-32

• Diagnostic ID from "Diagnose & Feedback" in the menu.
• a reproducible case if this is a bug, Dockerfiles FTW
• page URL if this is a docs issue or the name of a man page
• host distribution and version (Windows version, build number, etc)

Windows 10 Pro 15063.
This occurred after the latest Microsoft updates, installing the 'Creator Edition'

Steps to reproduce the behaviour

[wclr]

Too: Windows 10 Pro 15063, 'Creator Edition'

Every time I start windows I have this error and before docker is trying to start for a few minutes
A diagnostic was uploaded with id: D449E0EB-BA21-4703-BB58-FECB9D4ED103/2017-07-06_15-19-34

After I do restart docker, and it usually (*) starts ok (it takes too a few minutes) - quite long actually. But at least it works.

Some times it doesn't start with different errors:

Unable to create: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Inconsistent parameters PolicyStore PersistentStore and Dhcp Enabled


   at Docker.Backend.ContainerEngine.Linux.DoStart(Settings settings)
   at Docker.Backend.ContainerEngine.Linux.Restart(Settings settings)
   at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass9_0.<Register>b__0(Object[] parameters)
   at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)

[jasonbivins]

Hi @RealGandy
It looks like there was a problem with DNS during the install, or the network adapter isn't getting created properly.
Can you run this Debug script and share the results?
https://github.com/Microsoft/Virtualization-Documentation/tree/live/windows-server-container-tools/Debug-ContainerHost

[jasonbivins]

@whitecolor
If you turn off the Auto start function, and start Docker manually - do you get the same error?

[wclr]

Switched it off, will check next time I reset my PC.

[RealGandy]

@jasonbivins After the next reboot and manually starting docker it started running.

Output of the script attached.
Debug.output.txt

[jasonbivins]

@RealGandy - it looks like the virtual switch is either just slow to respond - or has some stale data.

The easiest way to solve this might just be to set Docker to use a fixed DNS address using the Network option in the GUI, or just toggle from auto to fixed - this will also trigger it to refresh the virtual adapter. If that doesn't work - there are some great troubleshooting tips for refreshing stale data here: https://docs.docker.com/docker-for-windows/troubleshoot/#networking-issues

Below is what I see in the log you shared:

[-] At least one NAT, Transparent, or L2Bridge Network exists 242ms
Expected {0} to be greater than {0}
206: $totalnets | Should BeGreaterThan 0
at , C:\Users\Gary\Downloads\Debug-ContainerHost.ps1: line 206
[-] NAT Network's vSwitch is internal 233ms
Expected: {Internal}
But was: {}
211: $switchType | Should Be "Internal"
at , C:\Users\Gary\Downloads\Debug-ContainerHost.ps1: line 211
[+] A Windows NAT is configured if a Docker NAT network exists 1.92s
[-] Specified Network Gateway IP for NAT network is assigned to Host vNIC 261ms
Expected: value to not be empty
225: $natGatewayIP | Should Not BeNullOrEmpty
at , C:\Users\Gary\Downloads\Debug-ContainerHost.ps1: line 225
[-] NAT Network's internal prefix does not overlap with external IP' 137ms
Expected {0} to be greater than {0}
252: $hostips.Count | Should BeGreaterThan 0
at , C:\Users\Gary\Downloads\Debug-ContainerHost.ps1: line 252

[wclr]

With autostart disabled and DNS fixed still started with 3rd try. It took about 6-7 minuts. Please analyze the log:

https://gist.github.com/whitecolor/8fd2100df1c77de2dd4f04e849303c54

[awidjaja]

I encountered the same issue:
#1119
Changing the DNS doesn't solve the issue.

Update: no more issue on Version 17.12.0-ce-rc2-win41 (14746).

[ctmcisco]

For anyone following this ticket:

Try the following:

1. Switch or stay on Windows Containers.
2. Disable the "Start when Windows starts" setting.

3. Exit Docker application
4. restart docker services via PowerShell

get-service docker | Restart-Service -Force -Verbose

5. Launch Docker , Run as Admin
6. Swtich to Linux Containers.

TEST:

Reboot Windows 10
Launch Docker
Does it work?

You can also parse the docker log in PowerShell for troubleshooting:

cat C:\Users\USERPROFILE\AppData\Local\Docker\log.txt -tail 10 -wait

[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