Docker hv-sock proxy (vsudd) is not reachable - win 10 pro crash on start

[skravtsov]

Expected behavior

Start Docker

Actual behavior

Crash on start.

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

Information

• Diagnostic ID from "Diagnose & Feedback" in the menu. 3D39A47D-B309-4A57-A800-D55982BE8150/2017-03-25_11-25-11
• host distribution and version (Windows version, build number, etc)

OS: Windows 10 Pro Edition: Professional Id: 1607 Build: 14393 BuildLabName: 14393.0.amd64fre.rs1_release.160715-1616

[NPrice99]

Same as #592 ?

[skravtsov]

NPrice99, looks like that. But what is the solution?

[NPrice99]

I wish I knew - there are a number of these "Docker hv-sock proxy (vsudd) is not reachable" issues on this repository, but nobody seems to be fixing them with a solution.

[schatzidogssss]

I just upgraded and am still having this. it occurs randomly and sometimes reboot will fix. I wondering if its a timing issue.

[skravtsov]

Any chance to be fixed or official problem solution?

[NPrice99]

An update to Docker came through tonight (28/03/2017) which has fixed the issue for me.

[schatzidogssss]

NPrice99 can you post the link? I don't see the update.

[NPrice99]

I just did "Check for Updates" on the Docker page

[ankursaini2006]

I had the same issue on my windows 10 laptop. I have been trying to resolve it for 4 days and finally I am able to resolve it.

Since my laptop is enterprise one so Docker on windows was not running on startup with Admin rights. Then I tried to open Docker for Windows.exe with "Run as Admin" and then it worked correctly.

I hope this would help others also who are facing the similar issue.

[mazki555]

I've encountered the same issues , (windows 10 pro , laptop)

What I've tried so far with no help: -trying to uninstall / reinstall both docker and hyper-v -running "Docker for Windows.exe" as admin didn't help

I've successfully installed docker on another laptop(exactly the same specs and version) 3 weeks ago.

Any further suggestions please ?

[ankursaini2006]

@mazki555 did you try "run as admin" as I mentioned in my previous post ?

[mazki555]

@ankursaini2006 Yes I did , it didn't help.

I just finished windows update and suddenly docker started running properly :~

Docker is working fine for me now , hope it helps someone .

[RafikFarhad]

Run as administrator works for me. Thanks @ankursaini2006 :)

[boukeversteegh]

Running windows updates worked for me

[igittGit]

Running windows updates caused the error for me

[frankkuo20]

Run as administrator works for me. Thank you !!

[Sandra-Young-Brighton]

Run as admin didn't work for me.

[zombiesplat]

windows update both caused and fixed the problem for me.

[devlace]

I'm also experiencing this error. Update + run as admin is not working for me.

[tony--]

Run as admin didn't work for me. Windows 1703 with latest updates, latest Docker for Windows.

[rwunsch]

1. "run as admin" did NOT work for me.
2. Windows update is update to the last updates (my company provides).

[sherryhw]

I have the same issue after I upgrade windows. Is there any way to resolve it?

[bijenkins]

Same issue. Windows 10 Pro.

[robertkalinowski]

Same issue, flustrating.... Microsoft Windows [Version 10.0.14393]

[robertlabrie]

Piling on here. Same issue on company issued laptop 1703 15063.483 Works correctly on personal laptop 1703 15063.540

[robertkalinowski]

Solved, problem was with rights to folder in which image is stored....

24.08.2017 01:46 "robertlabrie" notifications@github.com napisał(a):

Piling on here. Same issue on company issued laptop 1703 15063.483 Works correctly on personal laptop 1703 15063.540

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/docker/for-win/issues/606#issuecomment-324493076, or mute the thread https://github.com/notifications/unsubscribe-auth/AT2WfgmilwyW2tKqot4NkQicUJbu-wzWks5sbLnKgaJpZM4MpAiJ .

[robertlabrie]

@robertkalinowski C:\Users\Public\Documents\Hyper-V\Virtual hard disks?

[robertkalinowski]

yes, first time I corrected it just by going to the folder with image in file browser and system has proposed to give me all needed acceses....., so it was enoght to click OK.

After I upgraded dicker to new version and it stopped starting again, hovewer I weas able to go to directory without any problem, what I did this time to fix it was to check "Read Only" option on the image itself (when starting docker system showed error that image is read only and it cause problem) and I unset it back, and then docker was able to start....

just magic..... :-)

2017-08-24 2:17 GMT+02:00 robertlabrie notifications@github.com:

@robertkalinowski https://github.com/robertkalinowski C:\Users\Public\Documents\Hyper-V\Virtual hard disks?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/docker/for-win/issues/606#issuecomment-324497419, or mute the thread https://github.com/notifications/unsubscribe-auth/AT2Wfg92Bl-x135FtOl4jei4aPCQWTEsks5sbMEggaJpZM4MpAiJ .

[dopic]

Same problem here. It's really frustrating 👎

[robertkalinowski]

Solution is: 1) Install all Windows patches 2) Ensure your account have access to C:\Users\Public\Documents\Hyper-V\Virtual hard disks\MobyLinuxVM.vhdx (read/write access) 3) Ensure in Docker settings... Network you have correct proxy settings (if you are behind proxy -> for corpo laptops you need to set manual proxy settings)

After all should work....

2017-08-30 16:46 GMT+02:00 Douglas Picolotto notifications@github.com:

Same problem here. It's really frustrating 👎

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/docker/for-win/issues/606#issuecomment-326013852, or mute the thread https://github.com/notifications/unsubscribe-auth/AT2WfnCpbF3dgoeHhCZDhCW1Oxm9mrd5ks5sdXXNgaJpZM4MpAiJ .

[Workshop2]

Still getting this issue after allowing "Everyone" to have full control of that file.

[sachinb4u]

It worked after giving permissions to Creator Owner user

[edaemon]

I was also getting this error until I opened C:\Users\Public\Documents\. My system prompted me to grant permanent access for myself and that fixed the issue.

[jbc7ag]

I had the same error and I solved it installing the Docker Toolbox... next, next next, and then my 'Docker for windows' (as admin) ran without problems. Hope it helps

[dannybritto96]

D576239E-3746-40AE-AF71-50439F18D2A3/2017-10-04_09-09-17

[aurelien-xavier]

Run as administrator works also for me.

[araguacaima]

Run as administrator works also for me.

[robertmglynn]

Setting fixed DNS server settings solved this error in my case.

[alexhokl]

Running with Windows 10 Pro Version 1703 OS Build 15063.674 and restarting Docker from UI of Docker application works for me (without granting administrative rights).

[helletheone]

me too.. Still getting this issue after allowing "Everyone" to have full control of that file. and Restart of the Computer and Docker works again :)

[I-NOZex]

I always run docker as admin. Today suddenly, after I fresh start the computer today, I faced this issue. But to fix, all I needed to do was uncheck the "Expose daemon w/o TSL" Hope can help someone

[cmosguy]

I am having this issue, such a drag it randomly started occurring when i am using my companies laptop as well, and when i am at home not on my corporate network. I did exactly what @I-NOZex mentioned

I needed to do was uncheck the "Expose daemon w/o TSL"

And then now docker is starting properly again. What is the root cause here?

[alexivkin]

I was able to resolve this issue by adding an external switch (just a blank one) in the virtual switch configuration inside Hyper-V manager and restarting.

[tsasioglu]

Navigating to C:\Users\Public\Documents\Hyper-V\Virtual hard disks\ and requesting access, then restarting the Docker for Windows service fixed the issue for me.

[akshayrana30]

Navigating to \Hyper-V\Virtual Hard disks\ and requesting access, and then restarting the docker for windows as Admin fixed the issue of Docker hv-sock proxy (vsudd) is not reachable but now there is another error.

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.HyperV.RunScript(String action, Dictionary`2 parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\HyperV.cs:line 177
   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 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

[tnodet]

I updated to the latest version, gave full rights to Admins and current user in "C:\Users\Public\Documents\Hyper-V\Virtual hard disks\", rebooted Windows and Docker. It now works :)

[Charley1]

Maybe you'll roast me, but I had the same error from not having enought space on my C:/ Disk... Try to check it if you don't know where to go... Hope it could help someone

[Lufan]

Hello. I have this issue also on the latest docker version (17.12.0-ce-win46 (15048)). It happens when I try to restart the docker a lot of times (but not all times). After next time restart will work fine. (I need to restart the docker each time due to issue #573)

[allnightlong]

Got this error after auto-update to 17.12.0-ce-win47

[drinkbird]

@allnightlong me too. I solved it by visiting C:\Users\Public\Documents\Hyper-V\ then running docker as administrator