{"action":"opened","issue":{"url":"https://api.github.com/repos/docker/for-win/issues/277","repository_url":"https://api.github.com/repos/docker/for-win","labels_url":"https://api.github.com/repos/docker/for-win/issues/277/labels{/name}","comments_url":"https://api.github.com/repos/docker/for-win/issues/277/comments","events_url":"https://api.github.com/repos/docker/for-win/issues/277/events","html_url":"https://github.com/docker/for-win/issues/277","id":193155572,"number":277,"title":"docker 1.13.0-rc2: MobyLinuxVM doesn't get an IP","user":{"login":"robrich","id":664956,"avatar_url":"https://avatars.githubusercontent.com/u/664956?v=3","gravatar_id":"","url":"https://api.github.com/users/robrich","html_url":"https://github.com/robrich","followers_url":"https://api.github.com/users/robrich/followers","following_url":"https://api.github.com/users/robrich/following{/other_user}","gists_url":"https://api.github.com/users/robrich/gists{/gist_id}","starred_url":"https://api.github.com/users/robrich/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/robrich/subscriptions","organizations_url":"https://api.github.com/users/robrich/orgs","repos_url":"https://api.github.com/users/robrich/repos","events_url":"https://api.github.com/users/robrich/events{/privacy}","received_events_url":"https://api.github.com/users/robrich/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-12-02T16:17:50Z","updated_at":"2016-12-02T16:17:50Z","closed_at":null,"body":"Using Docker for Win 1.12.3-beta30.1 (see https://github.com/docker/for-win/issues/265) I would often get the message \"failed to get an IP 60 times\".  Restarting the VM a few times in the Hyper-V manager would solve the concern.\r\n\r\nAfter upgrading to Docker for Win 1.13.0-rc2, Docker no longer crashes on startup, and `docker run ...` now starts containers just fine.  But the VM doesn't get an IP address -- even after many restarts.  So I can't browse to running containers.  Diagnostic id `97E81F99-EBB6-4A27-8BE8-EA7A3C168EF4/2016-12-02_08-41-13`.\r\n\r\n`docker-machine create --driver hyperv machine` creates the machine successfully but times out with message `This machine has been allocated an IP address, but Docker Machine could not\r\nreach it successfully.`  Looking at Hyper-V manager, it got IPv6 address `fe80::215:5dff:febc` suggesting docker-machine create didn't wait long enough.  After running `@FOR /f \"tokens=*\" %i IN ('docker-machine env machine') DO @%i`, then running `docker pull node` errors with:\r\n\r\n```time=\"2016-12-02T09:04:31-07:00\" level=warning msg=\"Unable to use system certificate pool: crypto/x509: system root pool is not available on Windows\"\r\nUsing default tag: latest\r\nError response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:38020->[::1]:53: read: connection refused```\r\n\r\nMachine is Windows 10 Pro build 14393.447\r\nDocker for Windows version 1.12.3-beta30.1"}}
{"actor":{"display_login":"robrich"}}