VM "MobyLinuxVM": The VM couldn't get an IP address after 60 tries

Docker Desktop
, ,
41

Any chance of this multiple Internal Switch thing being fixed?

42

Hi Lee

we hope that we have fixed this issue in the beta which will be released this week. There were a number of issues which we finally managed to reproduce and debug.

There are still some issues with Windows networking when multiple NATs are configured. We will document this

rolf

43

Looking forward to the update. Is there a way to add a ‘debug’ or ‘verbose’ flag to get more output. Thanks

44

I think we have now uploaded Beta10 with a lot of improvements on the networking side.

We continue to improve logging and error diagnosis. Logs are located under AppData\Local\Docker so if you experience any issue getting a those would be very helpful.

Thanks
Rolf

1 Like
45

The issue of no IP address is fixed for me.

47

This is how I got it running

  1. Made sure that Acrylic DNS Proxy is not running. By stopping the service and making sure it doesn’t auto start
    This resolved

listen udp 10.0.75.1:53: bind: An attempt was made to access a socket in a way forbidden by its access permissions.

  1. I had an external USB Network adapter connected, I removed it and used the built-in adapter
    This resolved

Failed to start VM “MobyLinuxVM”: The VM couldn’t get an IP address after 60 tries

48

I’m new to the Docker for Windows beta and I’m having trouble with this issue. I’ve stepped through the comments in this thread but I’ve had no luck.

I’ve uploaded my logs in an attempt to get some help debugging this issue. http://pastebin.com/XrdEu6A0

Update:
I’ve tried uninstalling and reinstalling but that did not resolve the issue. I installed Docker on a fresh Windows 10 install so my hope is that there weren’t any applications or configurations that would cause issues.

49

Same issue here. Resolved by unintalling docker, disabled other virtual switches and reinstalled docker with latest msi.

50

Hi there. Got the same issue and tried all fixes listed above. none worked.
Then I tried to deactivate windows firewall and docker is working perfectly now.

51

I had the same issue on Windows 10 Pro and it was only resolved after I disabled AVG’s Firewall. Obviously, this is not a preferred solution. But you know, baby steps!

52

Afraid me too. Have removed and reinstalled from latest build, reset to factory setting, made sure that the Hyper-V logs are clean (they show no errors), made sure that no other Hyper-V switches exist, opened all Hyper-V services in the windows firewall. This only began happening in one of the recent builds (within the last three weeks, anyway, I’ve been away and the update when I came back and upgraded it was happening.)

Logs: http://pastebin.com/fsntDgH2

Thanks,

Derek

53

Docker is aware of this issue - see troubleshooting hints ( Networking Issue)
https://beta.docker.com/docs/windows/troubleshoot/

I had this and host of other errors since Docker Beta 12. It took me a while however what worked was disabling all DockerNAT adapter under Network Conection, remove DockerNAT from Hyper-V and remove MobyLinuxVM machine, uninstall Docker for Windows and reinstall ( or repair install ).
Additionally, under Control Panel->Network and Internet->Network Connections
right click on the ( ONLY ONE SHOULD BE PRESENT) vEthernet (DockerNAT) Properties and disabled IPV6 as well as Kaspersky NDIS 6 filter ( or any antivirus firewall you might have).

54

Ran into this same issue. New to docker beta. Windows 10 Enterprise Insider Preview. Build 14352.

  1. Downloaded and installed Docker for Windows beta.
  2. Docker attempted to install Hyper V, failed.
  3. Manually turned on hyper V and restart.
  4. Update docker and restart.
  5. Docker starts initializing. Get error about MobyLinuxVM not being able to get ip.
  6. Use docker menu Settings -> reset to default. Same error.
  7. Check Hyper V Manager, no additional NATs, just docker.
  8. Remove MobyLinuxVM and manually remove harddisk file. (Why is the hard disk stored in a shared location?)
  9. Manually delete everything. Attempt to manually create MobyLinuxVM from provided iso, HyperVM does not recognize the iso, image verification failed.

Docker Version 1.11.1-beta13 (build: 3441)

55

The networking issues look to have gone on for many releases. Same issue as above with DockerNAT. Tried all of the above including the instructions now included with the Windows Beta 13 Trouble shooting section without success.

56

It took some time to get an hopefully appropriate fix in place, but the upcoming Beta14 will remove the DHCP server and the VM will get it’s IP set address manually. Hopefully this will fix some of the issue. In a future Beta we are also likely removing the NAT switch altogether.

thanks for the patience and the reports.

57

thanks a lot.
it works!

58

What exactly do I have to do to fix the error?
I do not clarify much. There are different solutions.
Error: Unable to start: The VM could not get an IP address after 60 tries