Docker quick start terminal stops at 'Waiting for an IP..."

[raoonip]

Tried removing the default VM and creating new VM continuously waits for IP as shown in the following log

---

Microsoft Windows Version 10.0.10586 2015 Microsoft Corporation. All rights reserved.

C:\Users\Ram>docker-machine rm default
About to remove default
Are you sure? (y/n): y
Successfully removed default

C:\Users\Ram>docker-machine create -driver virtualbox default
Usage: docker-machine create [OPTIONS] [arg...]

Create a machine

Description:
Run 'docker-machine create --driver name' to include the create flags for that driver in the help text.

Options:

--driver, -d "none" Driver to create machine with.
--engine-install-url "https://get.docker.com" Custom URL to use for engine installation [$MACHINE_DOCKER_INSTALL_URL]
--engine-opt [--engine-opt option --engine-opt option] Specify arbitrary flags to include with the created engine in the form flag=value
--engine-insecure-registry [--engine-insecure-registry option --engine-insecure-registry option] Specify insecure registries to allow with the created engine
--engine-registry-mirror [--engine-registry-mirror option --engine-registry-mirror option] Specify registry mirrors to use
--engine-label [--engine-label option --engine-label option] Specify labels for the created engine
--engine-storage-driver Specify a storage driver to use with the engine
--engine-env [--engine-env option --engine-env option] Specify environment variables to set in the engine
--swarm Configure Machine with Swarm
--swarm-image "swarm:latest" Specify Docker image to use for Swarm [$MACHINE_SWARM_IMAGE]
--swarm-master Configure Machine to be a Swarm master
--swarm-discovery Discovery service to use with Swarm
--swarm-strategy "spread" Define a default scheduling strategy for Swarm
--swarm-opt [--swarm-opt option --swarm-opt option] Define arbitrary flags for swarm
--swarm-host "tcp://0.0.0.0:3376" ip/socket to listen on for Swarm master
--swarm-addr addr to advertise for Swarm (default: detect and use the machine IP)
--tls-san [--tls-san option --tls-san option] Support extra SANs for TLS certs

C:\Users\Ram>docker-machine create --driver virtualbox default
Running pre-create checks...
Creating machine...
(default) Copying C:\Users\Ram.docker\machine\cache\boot2docker.iso to C:\Users\Ram.docker\machine\machines\default\boot2docker.iso...
(default) Creating VirtualBox VM...
(default) Creating SSH key...
(default) Starting the VM...
(default) Check network to re-create if needed...

(default) Waiting for an IP...

Can someone Please help me in resolving the problem.

[mchiang0610]

@raoonip it looks like virtualbox is causing a lot of problems for you. Are you running windows 10 pro?

[AndreKR]

How long did you wait? I got this too, but several minutes later, while I was googling the problem, it continued successfully.

[scott-wood-vgh]

I am running Windows 10 Pro, and seem to be having an identical issue. It's been about 10 minutes.

[iver3on]

windows 10 insider preview 。similar .

[iver3on]

(default) Waiting for an IP...
Error creating machine: Error in driver during machine creation: Too many retries waiting for SSH to be available. Last
error: Maximum number of retries (60) exceeded
Looks like something went wrong in step ´Checking if machine default exists´... Press any key to continue...

[hoihoihoihoihoi]

I also have the same problem here.
im using virtualbox 5.0.12 r104815 along with DockerToolbox-1.12.0-rc2 on my windowsn10(pro)

just keep waiting for ip over 10 mins then the maximum retries errors come.
what to do next? pls help

[glight2000]

Same problem
Win10 DockerToolbox-1.11.2.exe
I tyied change visual box networking config. But no helps...

[hoihoihoihoihoi]

hey glight2000
i solved this problem by adding the rule to my windows10 firewall rules.

i wrote how it solves on my blog
http://acchi-muite-hoi.hatenablog.com/entry/2016/06/23/020317
im sorry its written in japanese lang,though i think you can figure it out by looking into the pictures

[hoihoihoihoihoi]

but then im gonna write down the steps here

1. uninstall your virtualbox and remove all registrys of it
2. reboot then install it again on youre cmd with VirtualBox-5.0.XXXX-Win.exe -msiparams NETWORKTYPE=NDIS5
3. go to control panels > security > then on firewalls > advance settings ( i dont know what its written on english)
4. and on Inbound Rules, create a new one
5. selecting the Custom mode.
   write the local IP there justlike what i wrote on my blog
   `

   192.168.99.1
   then
   192.168.99.0
   192.168.99.100
   `

6. choose public as youre profile
7. after that, make sure that the IP(192.168.99.1) configuration is same with the one on youre virtualbox hostonly adapters and in the one your network adapters(virtualbox hostonly adapter)
8. reboot, make docker-machine by the terminal docker-machine -d virtualbox default

i hope it helps !

[iver3on]

@hoihoihoihoihoi @glight2000 hi guys. any tips can not solve it. I solve it by reinstall my os and every thing goes well.

[iver3on]

hi guys. any tips can not solve it. I solve it by reinstall my os and every thing goes well.

[glight2000]

@hoihoihoihoihoi
Thank you very much for the steps. It doesn't work for me. The debug log shows that it can not get ip, because the host refused when create the default VM. And can not ping out size network.
I tried to close the Firewall too and doesn't work either. Maybe I missed something. But still thanks.

@iver3on
Yes, me too. Almost give up on win10...

[iver3on]

@glight2000 win10 can do it.but need reinstall win10.

[pedrobisp]

I had the same problem in windows 10 and the following worked for me:
"docker-machine rm default" in the command line, and then I run the docker quickstart terminal

[Ezekiel-DA]

Just ran into this; pretty sure my problem started after resetting the Windows Firewall to its default settings for unrelated reasons, which appears to have messed with Virtualbox's networks.

Uninstalling and re-installing VBox completely did the trick for me, hopefully this can help someone else !