Docker hv-sock proxy (vsudd) is not reachable

[Hinton]

Expected behavior

Docker starts.

Actual behavior

An error occurred

Information

Docker hv-sock proxy (vsudd) is not reachable
   at Docker.Backend.ContainerEngine.Linux.ConnectToVsud(TaskCompletionSource`1 vmId) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 293
   at Docker.Backend.ContainerEngine.Linux.DoStart(Settings settings, String daemonOptions) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 260
   at Docker.Backend.ContainerEngine.Linux.Start(Settings settings, String daemonOptions) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 130
   at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass9_0.<Register>b__0(Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeServer.cs:line 47
   at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeServer.cs:line 145

Diagnostic ID: E5D09B0C-1951-4398-93EE-7127C6343732/2018-03-21_13-53-48
Docker Version 17.12.0-ce-win47 (15139)

Windows Edition: Windows 10 Pro
Version: 1709
OS Build: 16299.309

Reinstalling and/or resetting docker dosn't help. Reverting to an older version helped for a while but the error occurred again after a while.

Steps to reproduce the behavior

1. Install Docker
2. Attempt to start Docker

[AnthonyMastrean]

I have this same problem, repeatedly, day after day. It starts with docker or docker-compose commands hanging. I go to the Docker for Windows application, open Settings, and try Reset | Restart Docker. I have tried quitting the Docker for Windows app and killing processes/services. Usually, I have to restart my machine 😢 .

Platform

I am completely up-to-date.

Edition: Windows 10 Pro
Version: 1709
OS Build: 16299.192

Application

I'm running stable Docker w/o experimental features.

Engine: 17.12.0-ce

Information

Docker hv-sock proxy (vsudd) is not reachable
   at Docker.Backend.ContainerEngine.Linux.ConnectToVsud(TaskCompletionSource`1 vmId) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 293
   at Docker.Backend.ContainerEngine.Linux.DoStart(Settings settings, String daemonOptions) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 260
   at Docker.Backend.ContainerEngine.Linux.Restart(Settings settings, String daemonOptions) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 189
   at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass9_0.<Register>b__0(Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeServer.cs:line 47
   at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeServer.cs:line 145

Diagnostic IDs

2018-03-19

• EC10B2E4-09D2-4873-84AF-24452C6B5916/2018-03-19_10-10-35
• EC10B2E4-09D2-4873-84AF-24452C6B5916/2018-03-19_10-14-20
• EC10B2E4-09D2-4873-84AF-24452C6B5916/2018-03-19_10-17-29

2018-03-22

• EC10B2E4-09D2-4873-84AF-24452C6B5916/2018-03-22_11-18-56
• EC10B2E4-09D2-4873-84AF-24452C6B5916/2018-03-22_11-24-10
• EC10B2E4-09D2-4873-84AF-24452C6B5916/2018-03-22_11-26-26
• EC10B2E4-09D2-4873-84AF-24452C6B5916/2018-03-22_11-39-34
• EC10B2E4-09D2-4873-84AF-24452C6B5916/2018-03-22_11-42-54

[AnthonyMastrean]

C'mon, there are dozens of similar open issues going back over a year! Most of these have no comments. The ones that do are from community members randomly changing settings.

What's happening here?

• Duplicates: Docker fails to start on Win 10 Enterprise #1860, Cannot write to database #1839, Unable to execute Start: Docker hv-sock proxy (vsudd) is not reachable [Windows 10 Enterprise] #1816, Docker hv-sock proxy (vsudd) is not reachable #1811, Docker fails to start - Docker hv-sock proxy (vsudd) is not reachable #1809, Docker hv-sock proxy (vsudd) is not reachable - win 10 pro crash on start #1776, Docker not starting on Windows 10 #1720, Docker hv-sock proxy (vsudd) is not reachable #1691, Docker hv-sock proxy (vsudd) is not reachable #1691, Docker hv-sock proxy (vsudd) is not reachable #1603, DFW on LCOW stoped working on the latest update #1590, [Notifications ][Error ] Docker hv-sock proxy (vsudd) is not reachable #1566, Docker fails to start with "Docker hv-sock proxy (vsudd) is not reachable" error #1557, Error upgrading to 17.12.0-ce-win47 (15139) #1545, Docker won't start while Folding@Home or BOINC is Running #1436, containerd issues [was: Docker hv-sock proxy (vsudd) is not reachable] #1359, Docker hv-sock proxy (vsudd) is not reachable #1279, Docker doesn't start #1152, Docker hv-sock proxy (vsudd) is not reachable #1110, Docker hv-sock proxy (vsudd) is not reachable #1096, Docker hv-sock (vsudd) is not reachable #1019, Docker for Windows don't start on Windows 10 Educations #1001, Docker hv-sock proxy (vsudd) is not reachable #971, Error Starting Docker in Windows 10 Docker hv-sock proxy (vsudd) is not reachable #904, Docker fails to start with error: Docker hv-sock proxy (vsudd) is not reachable #900, Docker fails to start both Linux & Windows containers #816, Docker hv-sock proxy (vsudd) is not reachable #792, Docker failing to start on Windows 10 #773, hv-sock proxy (vsudd) is not reachable #701, Docker hv-sock proxy (vsudd) is not reachable - WIN10 Enterprise LTSB #614, Docker hv-sock proxy (vsudd) is not reachable - win 10 pro crash on start #606, Docker hv-sock proxy (vsudd) is not reachable #592
• Related: Can't add Shared Drive - Firewall is blocking Sharing #1762 (comment), Multiple issues, -cannot connect to MobyLinuxVM Hyper-V Windows 10, Docker cannot connect to pipeline  #1592 (comment), Move MobyLinuxVM.vhdx to another drive  #1589 (comment), The process cannot access the file 'C:\WINDOWS\TEMP\<some file>' because it is being used by another process. #818 (comment), Can't start docker #648 (comment), Unable to create: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The object already exists. #599 (comment)

The only noted "workaround" in any of these issues seems rather sketchy... #1148 (comment)

[tylerreece22]

Yeah. I am having the same issue. Does anyone have the fix?

[tylerreece22]

Two things. One problem I was having was when I was downloading an image I ran out of memory and the this issue actually went away because I turned off the experimental features and that seemed to do the trick XD

[AnthonyMastrean]

I got the latest Docker for Windows update and I'm having the same "Docker hv-sock proxy (vsudd) is not reachable", but with a different stack trace.

Platform

I am completely up-to-date.

Edition: Windows 10 Pro
Version: 1709
OS Build: 16299.309

Application

I'm running stable Docker w/ experimental features.

Engine: 18.03.0-ce-win59 (16762)

Information

Docker hv-sock proxy (vsudd) is not reachable
   at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeClient.cs:line 36
   at Docker.Actions.DoStart(SynchronizationContext syncCtx, Boolean showWelcomeWindow, Boolean executeAfterStartCleanup) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 67
   at Docker.Actions.<>c__DisplayClass14_0.<Start>b__0() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 51
   at Docker.WPF.TaskQueue.<>c__DisplayClass19_0.<.ctor>b__1() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.WPF\TaskQueue.cs:line 59

Diagnostic IDs

2018-04-12

• EC10B2E4-09D2-4873-84AF-24452C6B5916/2018-04-12_11-34-10

[malawto]

I also get the dreaded Docker hv-sock proxy (vsudd) is not reachable error message. Docker for Windows was working until a Windows Update wrecked it. More, I think it has to do with being in a VM. It works on a physical box and I took the exact same steps to isolate and prove it (except I had to enable hypervisor applications for the VM inside of VMWare's settings. And I've done this with known working instances of Docker in the VM, so it's correctly set for sure.)

Here are the steps I took to reproduce it:

1. I spun up a new Windows 10 Pro machine on a physical box:
   Starting OS level
   Edition: Windows 10 Pro
   Version: 1709
   OS Build: 16299.125
2. Installed Docker CE for Windows Stable
   Everything works correctly. 🥇
3. Patch Windows...
   Updated OS
   Edition: Windows 10 Pro
   Version: 1709
   OS Build: 16299.371

Everything still works. But... do the same steps on a new VM, built the exact same way? It works after you install at OS Build: 16299.125, but somewhere in between that and getting to 16299.371... an update must break something.

It's clearly different running in a VM, but I've done it prior to the updates with no issue. Has something changed with communicating with the Hyper-V alpine VM while virtualized? Don't know, but I can isolate it to here. I don't have time to find the specific patch that 's responsible... and I think undoing patches is suboptimal, so I don't really want to.

[hoegge]

same as @AnthonyMastrean:
Docker hv-sock proxy (vsudd) is not reachable
at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeClient.cs:line 36
at Docker.Actions.DoStart(SynchronizationContext syncCtx, Boolean showWelcomeWindow, Boolean executeAfterStartCleanup) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 75
at Docker.Actions.<>c__DisplayClass15_0.b__0() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 59
at Docker.WPF.TaskQueue.<>c__DisplayClass19_0.<.ctor>b__1() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.WPF\TaskQueue.cs:line 59

Log: E9CBF190-66D5-420A-A5A8-9FA5D6D52443/2018-05-01_19-47-15

Stable Docker releases seems to be as likely as winning the lottery. When will I learn never to update

[Hinton]

I forgot about this issue. Docker for Windows have been working reliably for me lately, using version 18.03.0-ce-win59 (16762) on OS Build 16299.371.

Unfortunately I can't give any advice other than this specific version seems to work reliably on my two Windows 10 machines. I haven't dared to upgrade to the latest version and probably won't bother as long as it continues working.

[rn]

@hoegge in your case you actually run out of memory inside the Linux VM and the OOM killer starts killing processes. Try increasing the amount of memory allocated to the VM or increase the swap. Both via settings. You may also need to rest to factory as your virtual disk may be corrupted

[hoegge]

Tried to increase memory allocation from the default 2GB to 8GB since one of my containers was suddenly using 1,9 GB. Seems to have fixed the problem. Would be nice if docker warned about low memory instead of cryptic messages. Thanks @rn

[rn]

I've looked at all supplied diagnostics in this issue and other "Docker hv-sock proxy (vsudd) is not reachable" and they seem to fall into three categories:

• Running Docker for Windows inside a Windows 10 VM. This is problematic as we have no visibility of your Windows VM configuration and activity on the host. Because of that we can't support this configuration. See also https://docs.docker.com/docker-for-windows/troubleshoot/#running-docker-for-windows-in-nested-virtualization-scenarios
• The Linux VM is very slow booting. Please take a look at: Slow Linux VM boot [hv-sock proxy (vsudd) is not reachable] #1995
• There was a linux kernel crash of some sort. Please take a look at: Linux kernel crash/hung task [hv-sock proxy (vsudd) is not reachable] #1994

If you have provided a diagnostics ID, I've added you to the relevant issue, so I'm closing this issue.

[AnthonyMastrean]

@rn Thank you for digging though the diagnostics and identifying these two sub-categories! I'm going to watch the new issues and take a closer look at my diagnostics when the problem occurs again.

[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