search

docker / for-win

Bug reports for Docker Desktop for Windows
https://www.docker.com/products/docker#/windows
1.87k stars 288 forks source link

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

Closed skravtsov closed 6 years ago

skravtsov commented 7 years ago

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

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

markuspeloquin commented 6 years ago

I took a slightly more elegant approach (than giving Everyone access to the image) and added myself to the local Hyper-V Administrators group. I wonder if there's some policy on my work computer that is removing me from that group.

Giving Everyone access is the wrong solution. Running processes with admin access is the wrong solution. Least privilege, guys.

edit Plus, sometimes running an application with admin access causes files to be created/modified to only allow admins to access them, making it impossible to run an application as a non-elevated user in the future. This isn't necessarily the case here, but I've seen it happen in Linux.

bhatt40 commented 6 years ago

This issue has been wasting about two hours of my morning every day for the past two months. I've tried every solution that has been suggested here but nothing has worked. Is someone from the development team going to address this at some point? How do I increase its urgency, other than constantly filing bug reports and upvoting comments on this thread?

deroude commented 6 years ago

Turning off Experimental features in Settings>Daemon worked for me.

jahewett commented 6 years ago

Thanks @deroude this worked for me!

Turning off Experimental features in Settings>Daemon worked for me.

SaintFenix commented 6 years ago

Installing version: "Docker CE for Windows 17.11.0.14328-edge" through chocolatey got me around this error. Though I'd much prefer to be on a newer release, at least I can work now.

ronnelsantiago commented 6 years ago

Installing Docker CE for Windows 17.11.0.14328-edge from chocolatey did not work for me.

kamalbehera commented 6 years ago

I have checked Expose daemon on tcp://localhost... and its work for me Step to be followed: In windows docker notification icon right click and click Settings ->general -> checked Expose daemon on tcp://localhost.

gmreis commented 6 years ago

hi guys. Check the permission on path where stay the virtual disk of docker. I use Windows and I had to give permission to Virtual Machines. This may to is a solution.

jongio commented 6 years ago

Starting Docker as Admin fixed this for me.

fabinou commented 6 years ago

I had the same issue, tried all of those thing, with no success, and in fact i'll be able to start it, only when i had stopped another process that was eating all cpu. From there, Docker booted without problems. Hope it helps

isometriq commented 6 years ago

When running as Docker as admin, command-line seems to also require to be run as admin

froron commented 6 years ago

I tried all of these things, and this is what worked for me/happened to me: ( running on Windows 10 Enterprise, latest version with all updates done )

I tried to restart the laptop again and it started up fine (this time not running as administrator, and still not logged in to docker cloud).

AyushBhargav commented 6 years ago

I was getting the same error for stable version of docker. I uninstalled it and tried with edge version and it worked!

androlopez1 commented 6 years ago

Hello the solution is simple: Set the memory dedicated to docker to 1280MB in Settings (Right click in docker icon)-> Advanced. Then restart.

dwonga commented 6 years ago

Hello all! Finally, I resolved this issue (at least on my case).

I did everything to override it: run with administrator privileges, then as no administrator, stable version, edge version, remove windows updates, give all permission to everyone in VM folder, also tried disabling experimental features, etc, even format again windows! (uff). Two of them worked

1) Changing from linux containers to windows containers (right click on docker icon, then select 'windows container'). Restart, then return to linux container. But, if worked just for a few days. 2) The permanent solution is: a) using docker, edge version (remove other version and restart) b) give permission to eveyone C:\Users\Public\Documents\Hyper-V, it is not necesary to remove the 'read only', just give permission to all. c) Run docker, Docker hv-sock proxy error appears d) Docker settings > general > Enable "expose daemon on TCP without TLS". e) Run docker as admininstrator. You're done.

I hope it works for you.

Regards,

David.

Ian410 commented 6 years ago

@dwonga this worked for me.

The only change I did:

b) give permission to eveyone C:\Users\Public\Documents\Hyper-V, it is not necesary to remove the 'read only', just give permission to all.

AGeekInside commented 6 years ago

I resolved the issue by moving the location of the Hyper-V vm. It's the Images and volumes VHD location option in the Advanced Settings tab.

ghost commented 6 years ago

For those who may still see this problem, here's one fix:

Go to C:\Users\Public\Public Documents\Hyper-V , right click on Hyper-V, select Properties, and uncheck the "Read Only" box and apply changes. Then in the Windows task bar, right click on the red errored-out Docker icon, select Quit, then re-start it. Wait a minute for it to start, and it should work.

tosin2013 commented 6 years ago

It looks like a read-only issue. I fixed mine by changing the Images and volumes VHD location.

ghost commented 6 years ago

Since a week of two I'm also encountering this issue and each of the solutions above seem to fix it temporarily, but not permanently. About every 2 hours my Docker is freezing and I have to restart Docker for Windows, docker-compose twice (because of 502 Bad Gateway) and often even Hyper-V Moby-VM. It costs me a lot of time and it makes me less productive. Updates from Windows and Docker seem not to fix the issue. I still think it's mostly a CPU problem, but I can't be for sure as it's also happening when my computer is not using its swap memory. Extra RAM is at the moment not possible though. Docker is great when it works, but really a pain in the ass when it doesn't. Hope you guys from Docker will find a permanent solution for computers with less RAM memory... I still need this one until we can all switch to Macbooks with more memory.

dwonga commented 6 years ago

@eaunitrust , I just realize that, as you noticed, there are not permanent solutions. Let me suggest you what I did: Install docker toolbox. It is almost similar to docker for windows but without the hassles (and with no docker for windows container, but, who cares?)

mscrivo commented 6 years ago

For those that are getting this, are you running in a VM or bare metal? I have 2 bare metal machines where Docker works perfectly fine, and 2 Windows 10 1709 VMs (using latest version of VMWare Workstation), one of which I just created from scratch right now to try to get rid of this problem, that are exhibiting this problem.

The newly created VM has barely any software on it, only VS 2017, SQL Server express, git and a handful of other dev tools. So the fact that it's happening on this newly creating VM tells me that something broke (either in a recent Windows update or Docker) with Hyper-V virtualization within a VM. Wondering if anyone else can reproduce this?

Also, I would agree with the above posters, there's no permanent fix for this issue. Through some combination of running as admin, changing settings in Docker, you can often get it working for your current session, but it comes right back after reboot.

licor commented 6 years ago

Turn off the UAC solved the issue.

serbande commented 6 years ago

I have the same problems, first time it was ok if i reinstall docker but only until i do a restart of windows. Now i cant made it works even if i reinstall docker.

arthurdn commented 6 years ago

Removing or changing of priority for third party software with high CPU consumption fixed everything.

jamiegs commented 6 years ago

This issue causes me problems pretty frequently, many hours of lost productivity trying to get docker working again.

My environment, Windows 10 Pro 16299.248, in Parallels 12 VM, on High Sierra. Docker 10.12.0-win47.

It used to be I could consistently "fix" it by switching to windows containers, closing docker, the starting it as administrator. It's not working consistently for me any longer. I keep trying different orders of these methods until it eventually works. Each of these have got it working, but none consistently work for me.

Ian410 commented 6 years ago

I was having more issues even with changing permissions on the public folder. I ended up moving the Hyper-V folder to my users folder under the 'advanced' settings. Mine is currently: C:\Users\ian\Virtual Hard Disks\MobyLinuxVM.vhdx

I haven't had issues since.

marco-manza commented 6 years ago

In my case I had to select Reset to factory defaults and in few seconds docker was up and running.

twoez commented 6 years ago

@Ian410 , thanks a lot. You've pushed me in the right direction. I have finally solved this issue. However what I've done to solve the issue was slightly different:

I run the latest Edge 18.02.0-ce-win52 (15732) inside a VMWare guest.

Also note that giving full access to the "C:\Users\Public\Documents\Hyper-V" folder didn't work. Also trying several other permission relative settings I've tried didn't work.

Docker did work for a few days after installing Edge. However when I rebooted/shutdown Docker and tried to restart it didn't work anymore. I see a lot of posts of users saying installing Edge fixed this issue, but in fact it does until you reboot.

I have rebooted several times without any problems.

herman-rogers commented 6 years ago

Oddly run as admin also worked for me - Parallels, windows 10 dev, Docker Version 17.12.0-ce-win47.

fractalawareness commented 6 years ago

Had to switch from Edge to Stable to resolve the issue.

remarcbalisi commented 6 years ago

INCLUDE HOST!!!!!!!!!!!!!!!! docker -H tcp://0.0.0.0:2375 ps run hello-world

alinpop commented 6 years ago

What worked for me: Settings -> Reset -> Reset to factory defaults...

togakangaroo commented 6 years ago

Uploaded crash report with diagnostic id FEF3715C-5221-48BF-8B80-08BE2F82A6AA/2018-02-26_08-33-02

Windows 10, Parallels, Docker version 17.12.0-ce, build c97c6d6

mattbwt commented 6 years ago

I've had this problem since Christmas, every time my PC is restarted (Docker hv-sock proxy (vsudd) is not reachable)

I eventually get docker running after a combo of reinstalling/run as admin/disable experimental features

I found that a completely unrelated app on my PC (MSI Updater) is using a large amount of CPU (this app starts on PC restart). I uninstalled the app (and hence lowering the CPU%) and docker boots every time.

adarshrhegde commented 6 years ago

running docker as admin worked for me.

bhayanak commented 6 years ago

This issue is related to permission to "C:\Users\Public\Documents\Hyper-V\Virtual hard disks".

What i did is: copied "MobyLinuxVM.vhdx" from "C:\Users\Public\Documents\Hyper-V\Virtual hard disks" to some location for example "c:\docker\MobyLinuxVM.vhdx" give permission to all. Change vhdx file in Settings->Advanced. Now restart docker. it works.

hendrics commented 6 years ago

followed @twoez explanation and worked for me. Make sure to reboot a few times. Did a clean stable build as well.

rajeswari350626 commented 6 years ago

RUN AS ADMIN worked for me

Mr-Clam commented 6 years ago

Is this really a permissions thing, or is it either random luck that running as admin or faffing around with permissions solves this, or is that there are several issues that all manifest themselves with the same symptoms?

I've tried all of the suggestion here and in other tickets, but to no avail. This not surprising given the following: Docker works for me just fine if I directly boot my Mac in to BootCamp. Docker does not work for me if I boot the very same installation in a VMWare Fusion VM instead. About the only difference I can see is that it takes a lot longer for MobyLinux to start up when running in a VM. This used to work, but started failing for me roughly around the time I applied the Spectre/Meltdown patches to macOS and Windows 10, and also updated Docker, back in I guess January.

Is there a better and more effective/precise way to troubleshoot/debug this than trying all of these suggestions that apparently do work for some people, but clearly not all?

Mr-Clam commented 6 years ago

Are you asking me to check something? I already see MobyLinux starting and stopping in the Hyper-V Manager.

cmreigrut commented 6 years ago

I have the same problem, but only on a cold Windows startup. I dismiss the error message, Quit Docker and then run Docker for Windows again and it comes up just fine. I have not tried turning off Experimental features yet.

Mr-Clam commented 6 years ago

Does it help if you change the Docker for Windows service startup option from "Automatic" to "Automatic (delayed start)", or even to manual start? I can't help feeling there's a timing issue here, and at boot time there's a lot of other things loading at the same time.

cmreigrut commented 6 years ago

@nlmalc Good idea! I've just changed it to Delayed Start, and I'll let you know how it goes.

ghost commented 6 years ago

Win 10 Pro, Docker worked Fine. Then I installed Docker on a Win 10 Education. When Docker started up it asked to add Containers from Windows features otherwise it would not run. I said go ahead and I got the error. Went back to first machine and discovered that Containers was not turned on nor was it asked for. I turned it on and the error occurred. Turned it off and the error was gone. Will report on further testing.

cmeiklejohn commented 6 years ago

Weirdly enough, I also had this issue and it was resolved by making sure my laptop was plugged in when I started Docker.

ghost commented 6 years ago

A remark that uninstalling Git For Windows might help was the solution for me. It was installed on my laptop and not my desktop. The Containers Windows feature remains unchecked.

DanJ210 commented 6 years ago

Running as admin seems to have worked for me. I'm on corporate enviro as well. Though it only worked after I reset to factory settings so I'm hoping that this isn't an accident.

ph4wks commented 6 years ago

I've tried everything in this thread, on an Enterprise edition of W10 and still get the same error.

ghost commented 6 years ago

I suspect that there is a service or program that runs at start up is at the root of everyone’s problem. The modern guideline from MS is to no longer share dll files but I suspect some process has made their dll as the discovered version and thus interfering with Docker. In my case it was Git for Windows.

Ken Fogel Chairperson and Program Coordinater Computer Science Technology Dawson College 3040 Sherbrooke St. W Westmount, Quebec H3Z 1A4, Canada Tel: 514-931-8731 x 4799

From: Phil Hawkshaw notifications@github.com Sent: Thursday, March 15, 2018 3:59:51 AM To: docker/for-win Cc: Kenneth Fogel; Comment Subject: Re: [docker/for-win] Docker hv-sock proxy (vsudd) is not reachable - win 10 pro crash on start (#606)

I've tried everything in this thread, on an Enterprise edition of W10 and still get the same error.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/docker/for-win/issues/606#issuecomment-373291867, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALRk08Ny6gfEcEATK5oWKeCVAkRbTr_fks5teh93gaJpZM4MpAiJ.