{"action":"created","issue":{"url":"https://api.github.com/repos/docker/docker/issues/16265","labels_url":"https://api.github.com/repos/docker/docker/issues/16265/labels{/name}","comments_url":"https://api.github.com/repos/docker/docker/issues/16265/comments","events_url":"https://api.github.com/repos/docker/docker/issues/16265/events","html_url":"https://github.com/docker/docker/issues/16265","id":106224619,"number":16265,"title":"Cannot connect to docker after PC woken from sleep","user":{"login":"Mellbourn","id":1785727,"avatar_url":"https://avatars.githubusercontent.com/u/1785727?v=3","gravatar_id":"","url":"https://api.github.com/users/Mellbourn","html_url":"https://github.com/Mellbourn","followers_url":"https://api.github.com/users/Mellbourn/followers","following_url":"https://api.github.com/users/Mellbourn/following{/other_user}","gists_url":"https://api.github.com/users/Mellbourn/gists{/gist_id}","starred_url":"https://api.github.com/users/Mellbourn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Mellbourn/subscriptions","organizations_url":"https://api.github.com/users/Mellbourn/orgs","repos_url":"https://api.github.com/users/Mellbourn/repos","events_url":"https://api.github.com/users/Mellbourn/events{/privacy}","received_events_url":"https://api.github.com/users/Mellbourn/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-09-13T15:58:18Z","updated_at":"2015-09-19T14:05:10Z","closed_at":"2015-09-19T14:05:10Z","body":"I have just installed docker using [docker-toolbox 1.8.2][1] on Windows 10.\r\n\r\nDue to due to [this issue][2] I had to recreate the docker image using these commands\r\n\r\n    docker-machine rm default\r\n    docker-machine --native-ssh create -d virtualbox default\r\n\r\nAfter that it has been working fine, except for one problem:\r\n\r\nWhen the PC has gone to sleep and then wakes again, the docker commands can no longer connect. Example:\r\n\r\n    > docker images\r\n    An error occurred trying to connect: Get https://192.168.99.100:2376/v1.20/images/json: \r\n    dial tcp 192.168.99.100:2376: ConnectEx tcp: A connection attempt failed because the \r\n    connected party did not properly respond after a period of time, or established connection \r\n    failed because connected host has failed to respond.\r\n\r\nHowever the `docker-machine` lists the machine as running:\r\n\r\n    > docker-machine ls\r\n    NAME      ACTIVE   DRIVER       STATE     URL                         SWARM\r\n    default   *        virtualbox   Running   tcp://192.168.99.100:2376\r\n\r\nI can also confirm in VirtualBox that the VM screen seems to be active.\r\n\r\nI have tried starting and stopping the machine, but that does not help\r\n\r\n    C:\\x> docker-machine stop default\r\n    C:\\x> docker-machine start default\r\n    Starting VM...\r\n    Started machines may have new IP addresses. You may need to re-run the `docker-machine env` command.\r\n    C:\\x> docker-machine env default --shell=powershell\r\n\r\nIronically, the last command hangs, so I never get any environment settings.\r\n\r\nThe only thing that helps is to restart the whole PC. But that should be unnecessary?\r\n\r\nI have also posted this as [a question on StackOverflow][3]\r\n\r\nI am running\r\nDocker version 1.8.2, build 0a8c2e3\r\nOn Windows 10 Professional 64bit.\r\n\r\n    >uname -a\r\n    MSYS_NT-10.0 Phantom2 2.1.0(0.288/5/3) 2015-06-28 18:57 x86_64 Msys\r\n\r\n    C:\\x> docker info\r\n    Containers: 1\r\n    Images: 32\r\n    Storage Driver: aufs\r\n     Root Dir: /mnt/sda1/var/lib/docker/aufs\r\n     Backing Filesystem: extfs\r\n     Dirs: 34\r\n     Dirperm1 Supported: true\r\n    Execution Driver: native-0.2\r\n    Logging Driver: json-file\r\n    Kernel Version: 4.0.9-boot2docker\r\n    Operating System: Boot2Docker 1.8.2 (TCL 6.4); master : aba6192 - Thu Sep 10 20:58:17 UTC 2015\r\n    CPUs: 1\r\n    Total Memory: 996.2 MiB\r\n    Name: default\r\n    ID: DBFV:VWPR:CFZV:4KFH:THSV:YV3J:WV5J:T5TI:SFMP:7L27:JI5M:5PK6\r\n    Debug mode (server): true\r\n    File Descriptors: 12\r\n    Goroutines: 16\r\n    System Time: 2015-09-13T16:09:14.620288561Z\r\n    EventsListeners: 0\r\n    Init SHA1:\r\n    Init Path: /usr/local/bin/docker\r\n    Docker Root Dir: /mnt/sda1/var/lib/docker\r\n    Username: mellbourn\r\n    Registry: https://index.docker.io/v1/\r\n    Labels:\r\n     provider=virtualbox\r\n\r\n  [1]: https://www.docker.com/toolbox\r\n  [2]: https://github.com/kitematic/kitematic/issues/386#issuecomment-123804467\r\n  [3]: http://stackoverflow.com/questions/32547427/docker-unreachable-after-computer-sleep"},"comment":{"url":"https://api.github.com/repos/docker/docker/issues/comments/141671301","html_url":"https://github.com/docker/docker/issues/16265#issuecomment-141671301","issue_url":"https://api.github.com/repos/docker/docker/issues/16265","id":141671301,"user":{"login":"cpuguy83","id":799078,"avatar_url":"https://avatars.githubusercontent.com/u/799078?v=3","gravatar_id":"","url":"https://api.github.com/users/cpuguy83","html_url":"https://github.com/cpuguy83","followers_url":"https://api.github.com/users/cpuguy83/followers","following_url":"https://api.github.com/users/cpuguy83/following{/other_user}","gists_url":"https://api.github.com/users/cpuguy83/gists{/gist_id}","starred_url":"https://api.github.com/users/cpuguy83/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cpuguy83/subscriptions","organizations_url":"https://api.github.com/users/cpuguy83/orgs","repos_url":"https://api.github.com/users/cpuguy83/repos","events_url":"https://api.github.com/users/cpuguy83/events{/privacy}","received_events_url":"https://api.github.com/users/cpuguy83/received_events","type":"User","site_admin":false},"created_at":"2015-09-19T14:05:10Z","updated_at":"2015-09-19T14:05:10Z","body":"Hello, this does not look like the right repo for this issue.\r\nIt's probably an issue with virtualbox itself, but github.com/docker/docker-machine would be a better place for this.\r\nThanks!"}}