-
Notifications
You must be signed in to change notification settings - Fork 281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to start VM "MobyLinuxVM": The VM couldn't get an IP address after 60 tries #54
Comments
Hi @cuikangyi. Thanks for the bug report. Could you upload and provide a diagnostic ID for us to take a closer look? |
Also see #17 |
@rneugeba Thanks for your replay. and log [07:00:53.112][NamedPipeClient][Info ] Received response for DownloadVmLogs |
I have the same issue. Diagnostic loaded E29FCE66-DA9C-40C9-85CC-AD63831ADA03/2016-08-25_10-23-51 |
Would really like to see this get resolved. I have been getting this for a few days and have not been able to get it working after a few reinstalls. Its also on 2 different computers I use. A diagnostic was uploaded with id: 25FF9A46-6991-4935-885B-AE50E0FB18AC/2016-08-28_13-10-19 [18:20:27.179][NamedPipeClient][Error ] Unable to send Start: Failed to start VM "MobyLinuxVM": The VM couldn't get an IP address after 60 tries |
@runner7532 thanks for the report. Could you try the latest beta from https://download.docker.com/win/beta/InstallDocker.msi? It looks like in your case the Linux VM hasn't fully started and we made some omprovements in that area. |
Here is the Diagnostic ID for the beta version that I just installed If you want the log I will get that as well. |
Seem to be dealing w/ a similar issue, but am experiencing a Fatal error: Unable to execute Start: Unable to start: The VM couldn't get an IP address after 60 tries Version: 1.12.1-beta24 + latest Windows 10 update - build 14393 (1607 - KB3176938 8/31/16). Diagnostic ID - 6F013C72-7104-4907-BC8B-D7F1D42EE211/2016-08-31_20-09-12 Hyper-V Virtual Ethernet Adapter keeps creating "vEthernet (DockerNAT) 2" which Network Connections shows as an "unidentified network" with "no network access". NetworkInterfaceView shows vEthernet (DockerNAT) 2 as pointing to 10.0.75.1 Hyper-V Manager shows MobyLinuxVM as running, but the Network Adapter it's referencing is DockerNAT - which it lists as having "no communication". Not sure where the original DockerNAT vEthernet adapter is hiding, and causing the creation of vEthernet (DockerNAT) 2" [19:47:54.364][Program ][Info ] Version: 1.12.1-beta24 [19:50:59.257][NamedPipeServer][Info ] DownloadVmLogs done. |
Collating the reports from #17 into this issue: This was the report from @maxday: I'm running Docker for Windows Version: 1.12.0-beta21 on a WIN10 VM. The DNS server radio button configuration is set to "automatic". Error : Diagnostic id : |
Collating the reports from #17 into this issue: This was the report from @TaylorBarrick: A diagnostic was uploaded with id: F92E5AB4-A9AA-4269-A7D6-8FEB6F6E3D34/2016-08-01_22-30-16 [22:26:32.349][ApiProxy ][Info ] dns server: ready |
Collating the reports from #17 into this issue: This was the report from @kukjevov It looks like problem of Windows 10 Redstone 1 update (build 14393) with combination of latest stable docker version. I have enabled windows features like "Containers", "Hyper-V" and "Windows subsystem for linux (beta)". Nothing helped. And according this it looks like problem of Redstone 1. https://forums.docker.com/t/failed-to-start-vm-mobylinuxvm-the-vm-couldnt-get-an-ip-address-after-60-tries/19551/7 Have you solved this somehow ? |
I had a look at your logs and there seem to be a number of different issues:
As for @cuikangyi @runner7532 @Irieish @TaylorBarrick from the logs it appears like you all experience the same issue. The MobyLinuxVM boots fine, but then early during boot, it will try to contact the host via a Hyper-V technology called Hyper-V sockets but that connection never succeeds. I'm a little puzzled as to wy this is not working as I have several 14393 machines (and have tracked various insider builds over the past months) and have never seen this. Unfortunately, there is very little debugging support for this. Could you try updating with the latest windows updates and un-install and install Beta24 again? |
Thanks rneugeba. Will post back after uninstall/reinstall of Beta24. Believe Windows is current (installed latest update released 8/31 before posting). Windows 10 Pro (Version 1607 / Build 14393.105). |
Same error after reinstall of Beta24. Unable to start: The VM couldn't get an IP address after 60 tries Error log follows: [18:06:26.317][NamedPipeServer][Info ] DownloadVmLogs done. |
Hi. I have reported that there is problem with Redstone 1. I have multiple Windows installations and i tried it also on Windows 10 10586 and it worked without any problem. Then i tried it in work where i also have Windows 10 14393 Redstone 1 and it also worked. Only difference that i see now is that Redstone 1 where it is not working was upgraded from Insider Preview build and Redstone 1 where it is working was upgraded from stable 10586. I`m going to fully reinstall that one Windows to see if it helps. @rneugeba Before i reinstall i will gather requested informations. |
Hi, @kukjevov |
@rneugeba I managed to get working by first manually starting Docker and after that the next few re-boots were also fine. This morning however I had another failure on startup due to a different reason diagnostic is E29FCE66-DA9C-40C9-85CC-AD63831ADA03/2016-09-02_08-20-32 Again I can get going by manually starting Docker which is fine for my purposes. FYI - Hardware is only a couple of years old - Dell laptop with i7-4510U |
Unable to create: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Modifying the properties of the device 'Memory' failed. The operation cannot be performed while the object is in its current state. my most recent crash report: AD4A52AE-5334-4B98-8678-7191A2331558/2016-09-02_07-51-21 After the error above, I went into task manager and stopped all tasks I found for hyper-v and docker. I then opened hyper-v manager to verify that none of the VMs were running. I then opened Docker for Windows from the start menu. Doing this I was able to get the VM to boot and get the IP successfully. It appears to work correctly but does not. I then get the following error when trying to pull down a container:
Here is a copy of my log file, and a diagnostic was uploaded with id: As a test, I am setting my docker to not start when I login, but to allow me to start manually. The only issue that I have now is the DNS issue mentioned above. |
Hi, @rneugeba |
Hi @rneugeba |
Hi, here is my diagnostic ID for this problem: |
[EDIT] I now have the same problem. yesterday everything was working normal... but today docker is not getting its IP. Surface Pro 3 (128GB & 4GB RAM) (Have another Windows 10 Pro x64 as VM on ESXi 6 and it never worked as it never gets an IP. I know, that nested virtualization is probably not the most important thing on docker for windows... but I would use it ;) ) |
I had some success for a while, but a recent reboot triggered the old behavior. Diagnostic ID: 0D363E23-6B8A-4A91-AB4F-C0283E39F2B2/2016-09-07_15-43-48 |
Hi @rneugeba. Just installed beta25. Win10 Pro (1607 - build 14393.105). Slightly different error, but still not getting an IP address. Logs show everything pointing to DockerNAT, but the only adapter showing in devmgmt.msc, (including hidden) is vEthernet (DockerNAT) 2. Get-VMSwitch reveals DockerNAT as an Internal Switch, and Hyper-V shows MobyLinuxVM using DockerNAT as the connection, but with no IP and a status of "no communication". I was able to locate the mystery/ghosted DockerNAT ID within the debuginfo file, so could track down those entries in the registry, but wanted to roll this up first to see if there might be any better troubleshooting ideas. Thanks in advance for any help. Below is a copy of the log file, the Diagnostic ID, and error message. Diagnostic ID: 6F013C72-7104-4907-BC8B-D7F1D42EE211/2016-09-07_15-09-29 Unable to start: The VM couldn't get an IP address after 60 tries |
Have the same issue, clean install of Win 10 Pro 1607 build 14393.105. The VM never starts up have left it for 60+ minutes without it responding. Diagnostic ID: 21623F99-9384-43D1-99D9-97FD9FFA1CF3/2016-09-08_09-24-19 Get the same behaviour with the latest beta and the stable build. |
I was running Docker 1.12.1 with no issues, got the Error and done your fixes and it still not starting. This is the error now:
Here are my logs
|
@Gmanweb thanks for your report. Your issue is different. Could you please open a separate issue and also upload diagnostics as this collect additional information not contained in the logs. |
@rneugeba this too fool log start with this failure: After I restarted I started ok, this is the log with failure and then successful start: It seem to an old issue. |
I recently uploaded a diagnostic report D19FFA1C-8D0F-4773-8630-F5D2D1E32799/2016-11-14_17-14-06 Log Extract
Docker version
Windows 10 The Docker Network is configured for a different network (192.168.201.0/24). I cannot see any UDP listener on port 67 (DHCP) for that NIC I've previously tried removing all HyperV network switches and using the default Docker For Win settings too to no avail. |
Out of curiosity, why should I be seeing references to Vmware VMXNET3 and PVSCSI drivers on a HyperV based Virtual Machine. Seems a bit odd. |
An update: We now (again) have a fix in master which should ship with the next Beta (I'll close this issue once the Beta is out). Apologies that it took so long, but it required upstream Linux kernel changes, which took quite a while to track down. @glennsarti you see reference to Vmware VMXNET3 and PVSCSI drivers because the drivers are compiled into the kernel. So on boot it tries to probe them and it fails. This doesn't happen when the drivers are compiled as modules (but that has other issues). |
@rneugeba Thanks for the clarification! |
@rneugeba Can you confirm that this is supposed to be in 1.12.3-beta30.1 (8711). I couldn't see anything obvious in the release notes, and I still cannot start docker due to "...VM Couldn't get and IP Address..." |
@glennsarti we have not yet released a new version with the fix. |
@rneugeba Ahh ok sorry for the confusion. |
Finally, we released Beta31 https://download.docker.com/win/beta/InstallDocker.msi If you still experience this issue it might be worth opening a new issue, since this one is quite long... |
@rneugeba Confirmed, I can now start the Docker VM and it gets an IP Address. Thanks. (Docker Version 1.13.0-rc2-beta31 (9123)) |
I had the same issue, BETA working perfectly. |
Docker 1.12.6 wasn't working but 1.13.0 RC0 Beta37 works well. |
oooooh yay!! I've been missing kalabox on my windows 10 box, have been using the built in win10-Ubuntu as my localhost, which is definitely sweet, but obviously not as streamlined nor as feature rich as kalabox is with pantheon and all its glory. Cant wait to test it out, really wish I had checked back in sooner lol. |
Closed issues are locked after 30 days of inactivity. 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. |
[20:58:41.979][DockerService ][Info ] Version: 1.12.0-stable
[20:58:41.987][DockerService ][Info ] Starting on: 8/23/2016 8:58:41 PM
[20:58:41.995][DockerService ][Info ] Sha1: 9cd1dc28d3ac81cb5177ff9728f65200304b36f6
[20:58:42.579][BackendServer ][Info ] Started
[20:58:44.013][NamedPipeServer][Info ] Version()
[20:58:44.019][NamedPipeServer][Info ] Version done.
[20:58:44.723][NamedPipeServer][Info ] Stop()
[20:58:44.731][HyperV ][Info ] Stop
[20:58:44.751][PowerShell ][Info ] Run script with parameters: -Stop True...
[20:58:48.989][HyperV ][Info ] VM MobyLinuxVM is stopped
[20:58:49.007][NamedPipeServer][Info ] Stop done.
[20:58:49.033][NamedPipeServer][Info ] Start(Docker.Core.Settings)
[20:58:49.047][HyperVGuids ][Info ] Installing GUIDs...
[20:58:49.057][HyperVGuids ][Info ] GUIDs installed
[20:58:49.068][Firewall ][Info ] Opening ports for C:\Program Files\Docker\Docker\Resources\com.docker.proxy.exe...
[20:58:50.680][Firewall ][Info ] Ports are opened
[20:58:50.692][HyperV ][Info ] Create
[20:58:50.702][PowerShell ][Info ] Run script with parameters: -Create True -SwitchSubnetAddress 10.0.75.0 -SwitchSubnetMaskSize 24 -CPUs 2 -Memory 2048 -IsoFile C:\Program Files\Docker\Docker\Resources\mobylinux.iso...
[20:58:51.162][HyperV ][Info ] Using existing Switch: DockerNAT
[20:58:52.215][HyperV ][Info ] Using existing Switch IP address
[20:58:53.545][HyperV ][Info ] Using existing: MobyLinuxVM
[20:58:53.885][HyperV ][Info ] Setting MobyLinuxVM vm CPUs to 2 and Memory to 2048 MB
[20:58:53.896][DataKit ][Info ] Starting...
[20:58:53.906][PowerShell ][Info ] Run script...
[20:58:53.987][DataKit ][Info ] Started
[20:58:53.998][VpnKit ][Info ] Starting...
[20:58:54.010][PowerShell ][Info ] Run script...
[20:58:54.038][DataKit ][Info ]
[20:58:54.046][DataKit ][Info ] +11649us Datakit Starting com.docker.db.exe 16bb469 ...
[20:58:55.074][VpnKit ][Info ] Started
[20:58:55.093][ApiProxy ][Info ] Starting...
[20:58:55.105][PowerShell ][Info ] Run script...
[20:58:56.013][VpnKit ][Info ] com.docker.slirp.exe: Logging to stdout (stdout:true DEBUG:false)
[20:58:56.028][VpnKit ][Info ] com.docker.slirp.exe: Setting handler to ignore all SIGPIPE signals
[20:58:56.034][VpnKit ][Info ] com.docker.slirp.exe: vpnkit version %VERSION% with hostnet version local %HOSTNET_PINNED% uwt version 0.0.3 hvsock version 0.10.0 %HVSOCK_PINNED%
[20:58:56.042][VpnKit ][Info ] com.docker.slirp.exe: starting port_forwarding port_control_url:hyperv-connect://09a8824a-e88e-4bb4-aa91-ee60054eb72a max_connections:None vsock_path:
[20:58:56.049][VpnKit ][Info ] com.docker.slirp.exe: connecting to 09a8824a-e88e-4bb4-aa91-ee60054eb72a:0B95756A-9985-48AD-9470-78E060895BE7
[20:58:56.057][VpnKit ][Debug ] com.docker.slirp.exe: Waiting for connections on socket hyperv-connect://09a8824a-e88e-4bb4-aa91-ee60054eb72a
[20:58:56.064][VpnKit ][Warning] com.docker.slirp.exe: no database: using hardcoded network configuration values
[20:58:56.071][VpnKit ][Info ] com.docker.slirp.exe: connecting to 09a8824a-e88e-4bb4-aa91-ee60054eb72a:30D48B34-7D27-4B0B-AAAF-BBBED334DD59
[20:58:56.079][VpnKit ][Debug ] com.docker.slirp.exe: Waiting for connections on socket hyperv-connect://09a8824a-e88e-4bb4-aa91-ee60054eb72a
[20:58:57.059][ApiProxy ][Info ] Started
[20:58:57.073][Database ][Info ] Removing com.docker.driver.amd64-linux/proxy/exclude
[20:58:57.081][Database ][Info ] Removing com.docker.driver.amd64-linux/proxy/http
[20:58:57.087][Database ][Info ] Removing com.docker.driver.amd64-linux/proxy/https
[20:58:57.135][ApiProxy ][Info ] docker proxy (on deprecated port): ready
[20:58:57.146][ApiProxy ][Info ] dns server: ready
[20:58:57.154][ApiProxy ][Info ] docker proxy: ready
[20:58:57.325][DataKit ][Info ]
[20:58:57.332][DataKit ][Info ] +3299821us fs9p [ERROR] dispatcher caught Unix.Unix_error(Unix.EPIPE, "bytes_read", ""): no more requests will be handled
[20:58:59.012][Database ][Info ] Successfully removed 3 value(s)
[20:58:59.028][Database ][Info ] Writing com.docker.driver.amd64-linux/net/config=static
[20:58:59.034][Database ][Info ] Writing com.docker.driver.amd64-linux/net/address=10.0.75.2
[20:58:59.042][Database ][Info ] Writing com.docker.driver.amd64-linux/net/netmask=255.255.255.0
[20:58:59.050][Database ][Info ] Writing com.docker.driver.amd64-linux/net/gateway=10.0.75.1
[20:58:59.057][Database ][Info ] Writing com.docker.driver.amd64-linux/etc/resolv.conf=nameserver 10.0.75.1
[20:58:59.064][Database ][Info ] Writing com.docker.driver.amd64-linux/network=hybrid
[20:58:59.074][Database ][Info ] Writing com.docker.driver.amd64-linux/etc/docker/daemon.json={"registry-mirrors":[],"insecure-registries":[],"debug":false}
[20:58:59.082][Database ][Info ] Writing com.docker.driver.amd64-linux/etc/sysctl.conf=
[20:58:59.088][Database ][Info ] Writing com.docker.driver.amd64-linux/native/port-forwarding=true
[20:59:00.223][DataKit ][Info ]
[20:59:00.223][Database ][Info ] Successfully wrote 9 value(s)
[20:59:00.231][DataKit ][Info ] +6198121us fs9p [ERROR] dispatcher caught Unix.Unix_error(Unix.EPIPE, "bytes_read", ""): no more requests will be handled
[20:59:00.238][HyperV ][Info ] Start
[20:59:00.253][PowerShell ][Info ] Run script with parameters: -Start True...
[20:59:00.353][HyperV ][Info ] Starting VM MobyLinuxVM...
[20:59:01.878][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:02.967][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:04.006][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:05.040][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:06.117][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:07.806][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:08.837][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:09.872][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:10.912][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:11.965][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:13.673][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:14.716][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:15.771][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:16.814][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:17.867][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:19.484][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:20.536][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:21.581][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:22.636][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:23.711][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:25.278][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:26.309][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:27.340][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:28.392][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:29.438][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:31.083][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:32.132][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:33.167][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:34.205][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:35.262][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:36.822][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:37.872][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:38.905][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:39.979][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:41.053][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:42.658][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:43.717][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:44.766][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:45.827][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:46.901][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:48.489][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:49.552][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:50.608][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:51.639][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:52.706][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:54.305][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:55.373][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:56.430][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:57.473][HyperV ][Info ] Wait for the VM to get an IP address
[20:59:58.553][HyperV ][Info ] Wait for the VM to get an IP address
[21:00:00.120][HyperV ][Info ] Wait for the VM to get an IP address
[21:00:01.176][HyperV ][Info ] Wait for the VM to get an IP address
[21:00:02.225][HyperV ][Info ] Wait for the VM to get an IP address
[21:00:03.273][HyperV ][Info ] Wait for the VM to get an IP address
[21:00:04.340][HyperV ][Info ] Wait for the VM to get an IP address
[21:00:05.941][HyperV ][Info ] Wait for the VM to get an IP address
[21:00:07.007][HyperV ][Info ] Wait for the VM to get an IP address
[21:00:08.039][HyperV ][Info ] Wait for the VM to get an IP address
[21:00:09.074][HyperV ][Info ] Wait for the VM to get an IP address
[21:00:10.159][NamedPipeServer][Error ] Unable to execute Start: Failed to start VM "MobyLinuxVM": The VM couldn't get an IP address after 60 tries 在 System.Management.Automation.Runspaces.AsyncResult.EndInvoke()
在 System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
在 Docker.Core.PowerShell.Run(String script, Dictionary
2 parameters, Action
1 lineReceived)在 Docker.Backend.Backend.Start(Settings settings)
在 Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass7_0.b__0(Object[] parameters)
在 Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)
[21:00:10.203][NamedPipeServer][Info ] CheckInstallation()
[21:00:10.214][HyperV ][Info ] Check Hyper-V Windows optional feature
[21:00:10.225][PowerShell ][Info ] Run script...
[21:00:11.644][HyperV ][Info ] Hyper-V Windows feature is enabled
[21:00:11.654][NamedPipeServer][Info ] CheckInstallation done.
[21:00:11.702][NamedPipeServer][Info ] CheckHyperVState()
[21:00:11.714][HyperV ][Info ] Check Hyper-V State
[21:00:11.725][PowerShell ][Info ] Run script with parameters: -Check True...
[21:00:11.870][HyperV ][Info ] Hyper-V is running
[21:00:11.880][NamedPipeServer][Info ] CheckHyperVState done.
The text was updated successfully, but these errors were encountered: