{"action":"created","issue":{"url":"https://api.github.com/repos/docker/for-win/issues/1557","repository_url":"https://api.github.com/repos/docker/for-win","labels_url":"https://api.github.com/repos/docker/for-win/issues/1557/labels{/name}","comments_url":"https://api.github.com/repos/docker/for-win/issues/1557/comments","events_url":"https://api.github.com/repos/docker/for-win/issues/1557/events","html_url":"https://github.com/docker/for-win/issues/1557","id":288642751,"number":1557,"title":"Docker fails to start with \"Docker hv-sock proxy (vsudd) is not reachable\" error","user":{"login":"shawmanz32na","id":5596570,"avatar_url":"https://avatars2.githubusercontent.com/u/5596570?v=4","gravatar_id":"","url":"https://api.github.com/users/shawmanz32na","html_url":"https://github.com/shawmanz32na","followers_url":"https://api.github.com/users/shawmanz32na/followers","following_url":"https://api.github.com/users/shawmanz32na/following{/other_user}","gists_url":"https://api.github.com/users/shawmanz32na/gists{/gist_id}","starred_url":"https://api.github.com/users/shawmanz32na/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/shawmanz32na/subscriptions","organizations_url":"https://api.github.com/users/shawmanz32na/orgs","repos_url":"https://api.github.com/users/shawmanz32na/repos","events_url":"https://api.github.com/users/shawmanz32na/events{/privacy}","received_events_url":"https://api.github.com/users/shawmanz32na/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":36,"created_at":"2018-01-15T16:01:34Z","updated_at":"2018-05-03T13:14:54Z","closed_at":"2018-05-01T13:40:37Z","author_association":"NONE","body":"### Expected behavior\r\n\r\nDocker starts!\r\n\r\n### Actual behavior\r\n\r\nDocker fails to start, providing the following error:\r\n```\r\nDocker hv-sock proxy (vsudd) is not reachable\r\n   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\r\n   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\r\n   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\r\n   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\r\n   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\r\n```\r\n\r\nThis has affected me on both 17.12.0 builds. I've tried the basic troubleshooting including resetting Docker to factory defaults, restarting, and rebooting, each various times and in various orders, and I've still been unable to get Docker to start. I've uninstalled and reinstalled 17.09.1, and am back to work.\r\n\r\n### Information\r\n\r\n  - **Diagnostic ID**\r\n    5335669B-983C-4A00-A704-208023A88C15/2018-01-15_07-24-18\r\n  - **Windows version**\r\n    Windows 10 Pro Version 1709 (OS Build 16299.192)\r\n  - **Log**\r\n    [log.txt](https://github.com/docker/for-win/files/1632262/log.txt)\r\n\r\n\r\n### Steps to reproduce the behavior\r\n\r\n  1. Install either of the 17.12.0 Docker updates\r\n  2. Restart the machine (since Docker doesn't restart itself after an update - boo!)\r\n  3. Wait for Docker to fail\r\n"},"comment":{"url":"https://api.github.com/repos/docker/for-win/issues/comments/386291317","html_url":"https://github.com/docker/for-win/issues/1557#issuecomment-386291317","issue_url":"https://api.github.com/repos/docker/for-win/issues/1557","id":386291317,"user":{"login":"rn","id":3338098,"avatar_url":"https://avatars0.githubusercontent.com/u/3338098?v=4","gravatar_id":"","url":"https://api.github.com/users/rn","html_url":"https://github.com/rn","followers_url":"https://api.github.com/users/rn/followers","following_url":"https://api.github.com/users/rn/following{/other_user}","gists_url":"https://api.github.com/users/rn/gists{/gist_id}","starred_url":"https://api.github.com/users/rn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rn/subscriptions","organizations_url":"https://api.github.com/users/rn/orgs","repos_url":"https://api.github.com/users/rn/repos","events_url":"https://api.github.com/users/rn/events{/privacy}","received_events_url":"https://api.github.com/users/rn/received_events","type":"User","site_admin":false},"created_at":"2018-05-03T13:14:54Z","updated_at":"2018-05-03T13:14:54Z","author_association":"MEMBER","body":"@jcoconnor we used to run the Docker for Windows CI on ESX server spinning up very carefully configured windows VMs (3 per PR), and very beefy machines and had probably a 20%-30% failure rate either during startup or during test runs. We have since moved to bare-metal and the failures we have seen with nested virt are mostly gone. I probably also have looked at 50-100 issues with parallels and desktop virt, misconfigured VMs, underprovisioned VMs etc. We simply can't diagnose or help with these issue,"}}
{"actor":{"display_login":"rn"}}