Yes, I am playing (or trying to) with Docker. My first step is to install Docker and get it up and running. So far I am confident that I have all the prerequisites, however Docker fails to properly start with the following error:
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 267
at Docker.Backend.ContainerEngine.Linux.DoStart(Settings settings) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 251
at Docker.Backend.ContainerEngine.Linux.Start(Settings settings) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 123
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
Currently I am researching possible solutions to fix, however non of the suggestions has worked for me. If you have suggestions please feel free to comment and let me know.
Here is a systeminfo of the system I am testing with:
OS Name: Microsoft Windows 10 Enterprise
OS Version: 10.0.15063 N/A Build 15063
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
System Type: x64-based PC
Processor(s): 2 Processor(s) Installed.
[01]: Intel64 Family 6 Model 30 Stepping 5 GenuineIntel ~2926 Mhz
[02]: Intel64 Family 6 Model 30 Stepping 5 GenuineIntel ~2926 Mhz
Total Physical Memory: 4,096 MB
Available Physical Memory: 2,755 MB
Virtual Memory: Max Size: 4,800 MB
Virtual Memory: Available: 3,167 MB
Virtual Memory: In Use: 1,633 MB
One reply on “Docker hv-sock proxy (vsudd) is not reachable, Windows 10”
Hi,
I resolved this issue using this trick: https://github.com/docker/for-win/issues/971#issuecomment-329332671