{"action":"created","issue":{"url":"https://api.github.com/repos/docker/for-win/issues/606","repository_url":"https://api.github.com/repos/docker/for-win","labels_url":"https://api.github.com/repos/docker/for-win/issues/606/labels{/name}","comments_url":"https://api.github.com/repos/docker/for-win/issues/606/comments","events_url":"https://api.github.com/repos/docker/for-win/issues/606/events","html_url":"https://github.com/docker/for-win/issues/606","id":216959669,"number":606,"title":"Docker hv-sock proxy (vsudd) is not reachable - win 10 pro crash on start","user":{"login":"skravtsov","id":5462755,"avatar_url":"https://avatars1.githubusercontent.com/u/5462755?v=4","gravatar_id":"","url":"https://api.github.com/users/skravtsov","html_url":"https://github.com/skravtsov","followers_url":"https://api.github.com/users/skravtsov/followers","following_url":"https://api.github.com/users/skravtsov/following{/other_user}","gists_url":"https://api.github.com/users/skravtsov/gists{/gist_id}","starred_url":"https://api.github.com/users/skravtsov/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/skravtsov/subscriptions","organizations_url":"https://api.github.com/users/skravtsov/orgs","repos_url":"https://api.github.com/users/skravtsov/repos","events_url":"https://api.github.com/users/skravtsov/events{/privacy}","received_events_url":"https://api.github.com/users/skravtsov/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":112,"created_at":"2017-03-25T08:27:58Z","updated_at":"2018-05-01T17:15:40Z","closed_at":"2018-05-01T17:15:40Z","author_association":"NONE","body":"### Expected behavior\r\nStart Docker\r\n\r\n### Actual behavior\r\nCrash on start.\r\n\r\nDocker hv-sock proxy (vsudd) is not reachable\r\n   в Docker.Backend.ContainerEngine.Linux.ConnectToVsud(TaskCompletionSource`1 vmId)\r\n   в Docker.Backend.ContainerEngine.Linux.DoStart(Settings settings)\r\n   в Docker.Backend.ContainerEngine.Linux.Start(Settings settings)\r\n   в Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass8_0.<Register>b__0(Object[] parameters)\r\n   в Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)\r\n\r\n### Information\r\n\r\n  - Diagnostic ID from \"Diagnose & Feedback\" in the menu.\r\n3D39A47D-B309-4A57-A800-D55982BE8150/2017-03-25_11-25-11\r\n  - host distribution and version (Windows version, build number, etc)\r\n\r\nOS: Windows 10 Pro\r\nEdition: Professional\r\nId: 1607\r\nBuild: 14393\r\nBuildLabName: 14393.0.amd64fre.rs1_release.160715-1616\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/docker/for-win/issues/comments/385728505","html_url":"https://github.com/docker/for-win/issues/606#issuecomment-385728505","issue_url":"https://api.github.com/repos/docker/for-win/issues/606","id":385728505,"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-01T17:15:40Z","updated_at":"2018-05-01T17:15:40Z","author_association":"MEMBER","body":"@togakangaroo We don't support running Docker for Windows in a Windows 10 VM because we have no control over how you configure the VM (or what is happening on the host), see https://docs.docker.com/docker-for-windows/troubleshoot/#running-docker-for-windows-in-nested-virtualization-scenarios. Your Linux VM, inside the Windows VM is hung on calibrating the TSC, which I've seen may times, in particular with Parallels.\r\n\r\n@dannybritto96 your issue is different. A process (VPNKit) seem die. Can you please try the latest version of Docker for Windows. A lot of changes since when you filed the report.\r\n\r\n@skravtsov There is a Linux kernel crash in your logs (see below), actually there are several different ones, they all look related to the context switch code.\r\n\r\nIt looks like you have a skylake processor, which Linux detects and then tries to use the appropriate context switch code for that processor. Unfortunately, the version of Hyper-V does not correctly handle this processor. We had several issues like this in the past.\r\n\r\nI'm afraid the only solution is a Windows update. I don't know if this was fixed with a regular patch to build 14393 or if this requires an update to a newer Windows version.\r\n\r\nI'm closing this issue as Won't fix as this is not something we (Docker) can fix, but please report back if an update did fix it.\r\n\r\n\r\nThese were the only diagnostics IDs I could find in this issue. Closing"}}
{"actor":{"display_login":"rn"}}