Docker Community Forums

Share and learn in the Docker community.

Couldn't get an IP address after 60 tries

docker

(Manuelcr) #1

Hi,

I have been using Docker for Windows 10 since 3 months ago.

It was working fine with Hyper-V until the last Thursday (13th October), when I had to update the BIOS version of the motherboard.

After the new BIOS was installed, I had to enable VT-d and VT-x again.
At the next reboot Docker couldn’t start, giving the message ‘Failed to start VM “MobyLinuxVM”: The VM couldn’t get an IP address after 60 tries’.

I have searched at the forums and found some topics, for example:

But I have not been able to fix the problem.

I have uninstalled Docker and installed again. I have installed the BETA version. I have uninstalled the Hyper-V features and installed it again at Windows 10.

But I don’t get that Docker works again.

Any idea about it?

Do I need to configure any feature besides VT-d and VT-x at UEFI-BIOS?

Thanks.

Updated: uploaded crash report with diagnostic id: 7B679C05-8834-4D53-810C-CC5118C1A4CC/2016-10-18_19-23-34


(Manuelcr) #2

It seems that something is wrong with Docker.

I have installed Docker toolbook in a W7 notebook and i also have network problems with Docker & Virtual Box:

times, such confirmation window is minimized in the taskbar.
(default) Found a new host-only adapter: “VirtualBox Host-Only Ethernet Adapter
#10
(default) Windows might ask for the permission to configure a network adapter. S
ometimes, such confirmation window is minimized in the taskbar.
(default) Windows might ask for the permission to configure a dhcp server. Somet
imes, such confirmation window is minimized in the taskbar.
(default) Waiting for an IP…
(default) The host-only adapter is corrupted. Let’s stop the VM, fix the host-on
ly adapter and restart the VM
(default) Windows might ask for the permission to configure a network adapter. S
ometimes, such confirmation window is minimized in the taskbar.
(default) Waiting for an IP…
Waiting for machine to be running, this may take a few minutes…
Detecting operating system of created instance…
Waiting for SSH to be available…
Detecting the provisioner…
Provisioning with boot2docker…
Copying certs to the local machine directory…
Copying certs to the remote machine…
Setting Docker configuration on the remote daemon…

This machine has been allocated an IP address, but Docker Machine could not
reach it successfully.

SSH for the machine should still work, but connecting to exposed ports, such as
the Docker daemon port (usually :2376), may not work properly.

You may need to add the route manually, or use another related workaround.

This could be due to a VPN, proxy, or host file configuration issue.

You also might want to clear any VirtualBox host only interfaces you are not usi
ng.
Checking connection to Docker…
Error creating machine: Error checking the host: Error checking and/or regenerat
ing the certs: There was an error validating certificates for host “192.168.99.1
00:2376”: dial tcp 192.168.99.100:2376: connectex: No connection could be made b
ecause the target machine actively refused it.
You can attempt to regenerate them using ‘docker-machine regenerate-certs [name]
’.
Be advised that this will trigger a Docker daemon restart which will stop runnin
g containers.

Looks like something went wrong in step ´Checking if machine default exists´…
Press any key to continue…