Docker Community Forums

Share and learn in the Docker community.

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


(Taylorbarrick) #1

Expected behavior

Cannot start VM on build Win 10 14393

Actual behavior

Failed to start VM “MobyLinuxVM”: The VM couldn’t get an IP address after 60 tries
at Docker.Core.Pipe.NamedPipeClient.TrySend(String action, Object[] parameters)
at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters)
at Docker.Core.Backend.BackendClient.Start(Settings settings)
at Docker.Actions.<>c__DisplayClass26_0.b__0()
at Docker.Core.TaskQueue.<.ctor>b__16_0()

Information

A diagnostic was uploaded with id: F92E5AB4-A9AA-4269-A7D6-8FEB6F6E3D34/2016-08-01_22-30-16
Windows 10.0.14393

Steps to reproduce the behavior

  1. Starting Docker on boot.

From Log:

[22:26:32.349][ApiProxy ][Info ] dns server: ready
[22:26:32.353][ApiProxy ][Info ] docker proxy: ready
[22:26:32.356][ApiProxy ][Info ] listen tcp 10.0.75.1:53: bind: The requested address is not valid in its context.
[22:26:32.359][ApiProxy ][Info ] listen udp 10.0.75.1:53: bind: The requested address is not valid in its context.
[22:26:32.363][ApiProxy ][Info ] Waiting for the port/IP to become available
[22:26:32.367][ApiProxy ][Info ] Waiting for the port/IP to become available
[22:26:32.551][Database ][Info ] Successfully removed 3 value(s)
[22:26:32.555][Database ][Info ] Writing com.docker.driver.amd64-linux/net/config=static
[22:26:32.553][DataKit ][Info ]
[22:26:32.562][DataKit ][Info ] +524521us fs9p [ERROR] dispatcher caught Unix.Unix_error(Unix.EPIPE, “bytes_read”, “”): no more requests will be handled
[22:26:32.559][Database ][Info ] Writing com.docker.driver.amd64-linux/net/address=10.0.75.2
[22:26:32.570][Database ][Info ] Writing com.docker.driver.amd64-linux/net/netmask=255.255.255.0
[22:26:32.574][Database ][Info ] Writing com.docker.driver.amd64-linux/net/gateway=10.0.75.1
[22:26:32.579][Database ][Info ] Writing com.docker.driver.amd64-linux/etc/resolv.conf=nameserver 10.0.75.1
[22:26:32.583][Database ][Info ] Writing com.docker.driver.amd64-linux/network=hybrid
[22:26:32.586][Database ][Info ] Writing com.docker.driver.amd64-linux/etc/docker/daemon.json={“registry-mirrors”:[],“insecure-registries”:[],“debug”:false}
[22:26:32.591][Database ][Info ] Writing com.docker.driver.amd64-linux/etc/sysctl.conf=
[22:26:32.595][Database ][Info ] Writing com.docker.driver.amd64-linux/native/port-forwarding=true
[22:26:33.537][Database ][Info ] Successfully wrote 9 value(s)
[22:26:33.541][HyperV ][Info ] Start
[22:26:33.547][PowerShell ][Info ] Run script with parameters: -Start True…
[22:26:33.537][DataKit ][Info ]
[22:26:33.561][DataKit ][Info ] +1508337us fs9p [ERROR] dispatcher caught Unix.Unix_error(Unix.EPIPE, “bytes_read”, “”): no more requests will be handled
[22:26:33.631][HyperV ][Info ] Starting VM MobyLinuxVM…
[22:26:34.140][HyperV ][Info ] Wait for the VM to get an IP address
[22:26:35.155][HyperV ][Info ] Wait for the VM to get an IP address
[22:26:36.174][HyperV ][Info ] Wait for the VM to get an IP address
[22:26:37.434][HyperV ][Info ] Wait for the VM to get an IP address


[22:27:37.803][NamedPipeServer][Error ] Unable to execute Start: Failed to start VM “MobyLinuxVM”: The VM couldn’t get an IP address after 60 tries at System.Management.Automation.Runspaces.AsyncResult.EndInvoke()
at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
at Docker.Core.PowerShell.Run(String script, Dictionary2 parameters, Action1 lineReceived)
at Docker.Backend.Backend.Start(Settings settings)
at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass7_0.b__0(Object[] parameters)
at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)


Couldn't get an IP address after 60 tries
(Taylorbarrick) #2

Additionally, it keeps creating vEthernet (DockerNAT) 2, which see,s strange since I only have an Ethernet adapter and nothing else.


(Gabriel Machado) #3

Same is happening there too


(Schmorrison) #4

Seeing the same behavior here.


(Frankoctus) #5

+1 I have similar problem.


(Dodsky) #6

Upgraded to Windows 10 Anniversary Update and experienced the same issue. Saw some corrupted entries in networking interface using http://www.nirsoft.net/utils/network_interfaces.html. It seemed that everytime some corrupted network switch was added and docker failed to start because the corrupted interface reserved the default ip 10.0.75.0. Rolled back the updated and docker immediately worked like a charm. Skip the update for now.


(Taylorbarrick) #7

Yeah, I’ve been on the fast ring of updates, so I am wondering if I was
getting bit by that from previous builds. What build was working when you
rolled back?


(Dodsky) #8

I’ve rolled back to OS Build 10586.


(Cuikangyi) #9

+1 I have similar problem.


(Chrisdbarnett) #10

Hello, I have upgraded to build 14901.rs_prerelease.160805-1700 Windows 10 Preview on the insider program. I had the same, or a VERY similar issue and it’s now gone away.


(Chrisdbarnett) #11

I would try upgrading again. I have 2 machines, one on the Insider Preview programme and the other on just the normal Windows 10 Pro and both of my machines updated today to the latest and greatest that MS has to offer and they both work fine.

I admit, one always worked fine, but my main PC which is running under the MS Windows Insider Preview, previously could not run Docker. Now it can.


(Taylorbarrick) #12

Agreed, got the 14901.rs_prerelease.160805-1700 build today, and it seems to be working fine. Might turn off fast ring for a while now :slight_smile:


(Chrisdbarnett) #13

Be careful. Sadly, for me it was working just fine, now it’s broken again. One re-boot and it broke. Even worse, I managed to roll it all back to the standard Windows 10 Anniversary Edition - and it’s still broke. There has to be something else at play here. Mind you, I have not tried to re-install since. So I guess it’s time to give that a try.
Just be mentally prepared for it to break at some point again, just on the whim of a reboot.


(Taylorbarrick) #14

I have waited to avoid jinxing myself, but it seems to be holding steady for me after new insider builds. Current working versions:

14905.rs_prerelease.160811-1739 and 1.12.0-beta21 build 5971


(Taylorbarrick) #15

Well, I had some success for a while, but a recent reboot triggered the old behavior.

Current win build is 14915.rs_prerelease.160826-1902

Diagnostic ID: 0D363E23-6B8A-4A91-AB4F-C0283E39F2B2/2016-09-07_15-43-48

Unable to start: The VM couldn’t get an IP address after 60 tries
at , : line 332
at Docker.Backend.HyperV.RunScript(String action, Dictionary`2 parameters)
at Docker.Backend.ContainerEngine.Linux.DoStart(Settings settings)
at Docker.Backend.ContainerEngine.Linux.Start(Settings settings)
at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass7_0.b__0(Object[] parameters)
at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)


(Davidb71) #16

FYI, i ran into the same problem, but after searching forums and playing with options i finally got it running on Windows Anniversary Update keeping windows constantly updated. I read on a thread that the Docker Beta would integrate a newer Linux ISO correcting some issues about startup. So I adopted this version, but still ran in troubles. Then by clicking the tray-icon menu “Switch to Windows Containers”, the system configured itself and reboot again. Still having issues, I went to Docker web site configuration page and copy-paste the JSON configuration for windows and applied. No more chance… Then I cleaned up JSON configuration section and applied. The section filled automatically and Docker finally succeeded to run. During my experimentations I also configured network settings closer to what they are on my local network : subnet 192.168.1.0, DNS 192.168.1.254. Hope this helps.