{"action":"created","issue":{"url":"https://api.github.com/repos/docker/for-win/issues/311","repository_url":"https://api.github.com/repos/docker/for-win","labels_url":"https://api.github.com/repos/docker/for-win/issues/311/labels{/name}","comments_url":"https://api.github.com/repos/docker/for-win/issues/311/comments","events_url":"https://api.github.com/repos/docker/for-win/issues/311/events","html_url":"https://github.com/docker/for-win/issues/311","id":194847208,"number":311,"title":"Reset to Factory defaults in Docker stable version Windows 10 fails... ","user":{"login":"S3curityPlu5","id":3384853,"avatar_url":"https://avatars.githubusercontent.com/u/3384853?v=3","gravatar_id":"","url":"https://api.github.com/users/S3curityPlu5","html_url":"https://github.com/S3curityPlu5","followers_url":"https://api.github.com/users/S3curityPlu5/followers","following_url":"https://api.github.com/users/S3curityPlu5/following{/other_user}","gists_url":"https://api.github.com/users/S3curityPlu5/gists{/gist_id}","starred_url":"https://api.github.com/users/S3curityPlu5/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/S3curityPlu5/subscriptions","organizations_url":"https://api.github.com/users/S3curityPlu5/orgs","repos_url":"https://api.github.com/users/S3curityPlu5/repos","events_url":"https://api.github.com/users/S3curityPlu5/events{/privacy}","received_events_url":"https://api.github.com/users/S3curityPlu5/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-12-11T18:27:09Z","updated_at":"2016-12-12T11:50:58Z","closed_at":null,"body":"NOTE: I HAVE SOLVED THIS PROBLEM ... see last comment please for solution-\r\n### Expected behavior\r\nReset to Factory defaults should bring windows 10 pro to working container host,\r\n\r\n### Actual behavior\r\nDocker Error popup displays: \r\nReceives error: Unable to start: The VM couldn't get an IP address after 60 tries\r\nat Fatal, <No file>: line 353\r\nat Start-MobyLinuxVM, <No file>: line 267\r\nat <ScriptBlock>, <No file>: line 363\r\n   at Docker.Backend.HyperV.RunScript(String action, Dictionary`2 parameters)\r\n   at Docker.Backend.ContainerEngine.Linux.DoStart(Settings settings)\r\n   at Docker.ContainerEngine.Linux.Start(Settings settings)\r\n   at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass8_0.<Register>b__0(Object[] parameters)\r\n   at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)\r\nAFTER renaming old VM to OLDmobylinux, then reset to defaults again, but new VM was created and after running command docker images : \r\nreceive the following \r\nAn error occurred trying to connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/images/json: open //./pipe/docker_engine: The system cannot find the file specified.\r\n### Information\r\nCannot get back to working state, No reason why cannot get an ip address, doesn't make sense, only one docker Nat network adapter set to default address settings, \r\n\r\nDiagnostic ID = 6696D7DE-88FD-44F5-90F6-BFAE1E91BD10/2016-12-11_13-22-30\r\n\r\nThis is a bug with my system, but would like to see why this cannot be fixed.\r\n  - Diagnostic ID from \"Diagnose & Feedback\" in the menu.\r\n  - a reproducible case if this is a bug, Dockerfiles FTW\r\n  - page URL if this is a docs issue or the name of a man page\r\n  - host distribution and version (Windows version, build number, etc)\r\n\r\n### Steps to reproduce the behavior\r\n\r\n  1. ... Rename old VM to OLDMOBYVM\r\n  2. ...Reset to factory defaults\r\n  "},"comment":{"url":"https://api.github.com/repos/docker/for-win/issues/comments/266411723","html_url":"https://github.com/docker/for-win/issues/311#issuecomment-266411723","issue_url":"https://api.github.com/repos/docker/for-win/issues/311","id":266411723,"user":{"login":"S3curityPlu5","id":3384853,"avatar_url":"https://avatars.githubusercontent.com/u/3384853?v=3","gravatar_id":"","url":"https://api.github.com/users/S3curityPlu5","html_url":"https://github.com/S3curityPlu5","followers_url":"https://api.github.com/users/S3curityPlu5/followers","following_url":"https://api.github.com/users/S3curityPlu5/following{/other_user}","gists_url":"https://api.github.com/users/S3curityPlu5/gists{/gist_id}","starred_url":"https://api.github.com/users/S3curityPlu5/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/S3curityPlu5/subscriptions","organizations_url":"https://api.github.com/users/S3curityPlu5/orgs","repos_url":"https://api.github.com/users/S3curityPlu5/repos","events_url":"https://api.github.com/users/S3curityPlu5/events{/privacy}","received_events_url":"https://api.github.com/users/S3curityPlu5/received_events","type":"User","site_admin":false},"created_at":"2016-12-12T11:50:58Z","updated_at":"2016-12-12T11:50:58Z","body":"Since this is still open I should comment that although I am able to run docker containers, the docker daemon, or engine (dockerd service) is still refusing to start, when attempting to start from command line receive the following error:  level=fatal msg=\"unable to configure the Docker daemon with file \r\nC:\\\\ProgramData\\\\docker\\\\config\\\\daemon.json: json: cannot unmarshal string into Go value of type bool\\n\r\nkitematic now displays containers and can start and stop them, and there is now another service the com.docker.service running successfully but the docker engine refuses to start, I have set the config file to defaults, and taken out tlc verify= true, because of tls cert errors when it was true.\r\n"}}
{"actor":{"display_login":"S3curityPlu5"}}