Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Unable to start: The VM couldn't get an IP address after 60 tries #45

Closed
juherr opened this issue Aug 18, 2016 · 4 comments
Closed

Unable to start: The VM couldn't get an IP address after 60 tries #45

juherr opened this issue Aug 18, 2016 · 4 comments

Comments

@juherr
Copy link

juherr commented Aug 18, 2016

Expected behavior

Upgrade and start.
Or provide a better message in case of issue.

Actual behavior

First, I tried the auto update which failed without any message (docker didn't start or started with the previous version).
Then, I tried a manual update which worked well but at the start I received:

Unable to start: The VM couldn't get an IP address after 60 tries
à Fatal, <Aucun fichier> : ligne 313
à Start-MobyLinuxVM, <Aucun fichier> : ligne 233
à <ScriptBlock>, <Aucun fichier> : ligne 322
   à Docker.Backend.HyperV.RunScript(String action, Dictionary`2 parameters)
   à Docker.Backend.LinuxContainersEngine.DoStart(Settings settings)
   à Docker.Backend.LinuxContainersEngine.Start(Settings settings)
   à Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass7_0.<Register>b__0(Object[] parameters)
   à Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)

Information

  • Diagnostic ID: 63FC49AC-136A-4694-8FC1-E651A239AEE3/2016-08-18_09-42-11
  • host distribution: Windows 10.0.14393

Steps to reproduce the behavior

  1. Upgrade to beta23
  2. Try to start

Fix:
I had 127.0.0.1 docker.local in my hosts file to solve a previous issue. When I remove it, docker is running well.

@rn
Copy link
Contributor

rn commented Aug 18, 2016

@juherr Thanks for your report.I tried to reproduce and added 127.0.0.1 docker.local to C:\Windows\System32\drivers\etc\hosts and I could start The app just fine. Did you change anything else?

@juherr
Copy link
Author

juherr commented Aug 18, 2016

@rneugeba Maybe the fix didn't fix. I've just added the configuration in my host again, and docker is running now.

@rn
Copy link
Contributor

rn commented Aug 18, 2016

Thanks for getting back to me. I'm closing this issue as it seems to have fixed itself for you. We still have a related issue (#17) open in any case.

@rn rn closed this as completed Aug 18, 2016
@amd5 amd5 mentioned this issue Dec 3, 2019
@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Jun 17, 2020
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Projects
None yet
Development

No branches or pull requests

3 participants