"Machine IP Could Not Be Fetched" and other errors

[scottAnselmo]

When running Kitematic I get errors no matter what option when I select. When initially running Kitematic after installing the toolbox and creating the VM w/ Kitematic or otherwise clicking "Delete VM and Retry Setup" upon getting the initial error I get:

"C:\Program Files\Docker Toolbox\kitematic\resources\resources\docker-machine.exe -D create -d virtualbox --virtualbox-memory 2048 default returned non zero exit code. Stderr: Converting from raw image file="stdin" to file="C:\Users\disk.vmdk"... Creating dynamic image with size 20971520000 bytes (20000MB)... Error creating machine: exit status 1 You will want to check the provider to make sure the machine and associated resources were properly removed."

if I click "Retry Setup" I instead get:

"Machine IP could not be fetched. Please retry the setup. If this fails please file a ticket on our GitHub repo."

For what it's worth I'm running Windows 8.1 x64.

[nathanleclaire]

Very unfortunate. Could you re-try with the latest test build from virtualbox.org?

[scottAnselmo]

Even with VB 5.0.3 the issue persists.

[cyoung35]

I to am receiving this same error using Windows 7 sp1.: $ docker version Client: Version: 1.8.1 API version: 1.20 Go version: go1.4.2 Git commit: d12ea79 Built: Thu Aug 13 02:49:29 UTC 2015 OS/Arch: windows/amd64 Get http://127.0.0.1:2375/v1.20/version: dial tcp 127.0.0.1:2375: ConnectEx tcp: No connection could be made because the target machine actively refused it..

• Are you trying to connect to a TLS-enabled daemon without TLS?
• Is your docker daemon up and running?

[nathanleclaire]

@cyoung35 If you do eval $(docker-machine env default) before trying the Docker command does it work?

[L-four]

I managed to get around this by downloading the test version of Virtualbox and replacing the installer that comes with Kinematic .\VirtualBox-5.0.3-102467-Win.exe --extract copy VirtualBox-5.0.3-r102467-MultiArch_<myArch>.msi and common.cab from C:\Users\<myUser>\AppData\Local\Temp\VirtualBox\ to C:\Program Files\Docker Toolbox\installers\virtualbox\ edit: rename VirtualBox-5.0.3-r102467-MultiArch_<myArch>.msi to virtualbox.msi

Start Kitematic

Enjoy

[marfago]

Same error on Windows7 SP1

[ocxo]

I had a similar issue on OS X that traced back to a weird fallback ssh config. Is there possibly some sort of local network config or firewall blocking the communication on 2375?

[cfossace]

Me too on Windows 7 @marfago let me know if you find a solution

[mskutin]

The same issue, Windows Server 2012 R2

[vrbilgi]

Same issue for me Windows 7 Version 2.2

[hsachdevah]

Same issues on windows 10 as well

[dgageot]

I suggest this plan to start really fresh:

• Delete all existing virtualbox machines
• Delete all ghost VM that might remain in virtualbox GUI
• Upgrade to the latest Toolbox. Make sure Virtualbox version is 5.0.14
• Delete all host-only interfaces in Virtualbox GUI
• Create a new default docker machine

Please tell me if it fixes the issue for any if you

[dhallam]

I had a number of issues, including the "Machine IP could not be fetched." issue. Running on Win10. Updated VirtualBox from 5.0.10 to 5.0.14, did not remove an existing VM and Kinematic has started fine.

[sghosh-sg]

I managed to get around this by downloading the test version of Virtualbox and replacing the installer that comes with Kinematic .\VirtualBox-5.0.3-102467-Win.exe --extract copy VirtualBox-5.0.3-r102467-MultiArch_<myArch>.msi and common.cab from C:\Users\<myUser>\AppData\Local\Temp\VirtualBox\ to C:\Program Files\Docker Toolbox\installers\virtualbox\ edit: rename VirtualBox-5.0.3-r102467-MultiArch_<myArch>.msi to virtualbox.msi

Start Kitematic

Enjoy

Buddy...you are a genius. Saved my day. Thanks a ton.