Failed to get machine "boot2docker-vm": machine does not exist
Opened this issue · 28 comments
I just did a clean install on windows 64.
when i type "boot2docker start" i get:
Failed to get machine "boot2docker-vm": machine does not exist
any ideas ???
Oracle VirtBox is there:
C:\Program Files\Oracle\VirtualBox
OK i found the Bug.
Its to do with aleady having GIT installed, as most will !
Basically the current installer (for me with Git already installed) default to NOT install Git).
This means that the start script fails i presume: See the following code lines:
convert any C:/ into /c/ as MSYS needs this form
B2DPATH=${B2DPATH//C:///c/}
So, i removed boot3docker, VBox and Git
Then a clean install
Everything works.
Suggest fix.
Check for GIT already being installed and where its path is.
Please fix for next version. Have given enough context of problem here i think...
This error occured for me also, even I had MSysGit pre-installed.
But if you run
$ boot2docker initit will fix the case
it creates the missing "bootdocker-vm", which is supposed to happen via "start.sh" in installed artifacts but doesn't take place
I have the same symptoms when I already had Git and VirtualBox installed. boot2docker init didn't fix things in my case as now I'm getting an error that ssh-keygen isn't found in the path. I'll fix this manually.
if only we could run all this stuff in a container and not need to worry about what you had already installed and customised :/
if someone works it out and can send a patch, it'll be fixed - detecting that someone has installed git in Z:\somewhere\tools\git is kinda hard (er, duh - I'll see if i can find it in the registry, its been way too long since i worked on windows)
@SvenDowideit I'll see if I can create a patch for this scenario on all dependencies, the fix shall go in https://github.com/boot2docker/windows-installer right, or somewhere else
yup, windows-installer
for me same problem dint appear when i used start.sh from git bash prompt.
👍
good job!
@abhishekkr's suggestion is right;
$ boot2docker init fixes case
I use Windows 7 and $ boot2docker init doesn't work for me. It replies with:
error in run: Failed to initialize machine "boot2docker-vm": exit status 1
I tried this after boot2docker complete reinstall.
Same problem as @Toshakins on OS X
Had the same problem (Win7 64bit) and found a solution at boot2docker/windows-installer#31 - most important I had to remove the folder boot2docker-vm at "C:\Users\username\VirtualBox VMs" from a previous installation.
@SvenDowideit I don't think you need to check the registry, just look in the path. If someone already has Git installed, it's highly likely that they've put it in their path.
If it isn't in the path then they wouldn't be expecting the installer to be able to use the already-installed version.
Hi,
it seems I got it working. I posted my answer here: http://stackoverflow.com/questions/25377392/how-to-initialize-and-run-docker-on-windows/27527075#27527075
You need to activate Intel Virtualization Technologies and choose a 64-bit linux version for the virtual image. Then boot with the Boot2docker image (which is also 64 bit).
FYI, I'm in a mac and I also seem to have the same problem which led me to this page:
$ boot2docker start
error in run: Failed to get machine "boot2docker-vm": machine does not exist (Did you run `boot2docker init`?)
To which I enter boot2docker init command and I get the following:
error in run: Failed to initialize machine "boot2docker-vm": exit status 1
I'm having the same issue, on OS X 10.10.3.
$ boot2docker init
runs fine, but when I do:
$ boot2docker up
I get the following error:
error in run: Failed to start machine "boot2docker-vm": exit status 1
I'm getting the same issues as @theMicMac and @damianesteban on my Mac. Oddly, it only started yesterday after I upgraded VirtualBox - but despite downgrading again, and installing with and without brew/cask, I still get the same issues.
The VM seems to start fine, as far as VBox is concerned, but it's like boot2docker can't communicate with it.
finally got it to work again. I think my boot2docker ISO was corrupted or something and I was assuming (I know...) that it was getting the ISO fresh every time I did a brew install boot2docker.
boot2docker delete
brew uninstall docker
brew uninstall boot2docker
rm -rf /Users/<your-username>/.boot2docker/
rm -rf /Users/<your-username>/VirtualBox\ VMs/boot2docker-vm
brew install boot2docker
boot2docker init
boot2docker up
What worked for me was a simple copy of ssh key(private) which I already had for the pre-installed git.
Go to c:/user/YOU/.ssh/ then
copy id_rsa id_boot2docker
then run
boot2docker init
It should work.
If you're on Windows, make sure your virtualization options are turned on in the BIOS. Many vendors ship with this option turned off (go figure).
I removed boot2docker-vm from GUI and had the same problem for Mac OS (can not run any boot2docker command). I did following and works fine (incase some one has the same problem):
rm -rf /Users//VirtualBox\ VMs/boot2docker-vm
boot2docker init
boot2docker up
(be aware of new docker settings)
Windows 8.1 64bit here. I had the same error as many others:
error in run: Failed to start machine "boot2docker-vm": exit status 1
To help diagnose the error, I launched VirtualBox directly and tried to run boot2docker. I ended up getting an error related to VT-x not being enabled/available (VirtualBox trouble ticket).
For me, the solution was uninstalling Hyper-V via Programs and Features. After un-installing and a reboot, I had no issues.
boot2docker-vm had assigned a memory greater than the physical memory of my pc.
In order to resolve this error
error in run: Failed to start machine "boot2docker-vm": exit status 1
i have decreased the to a lower value.
@SvenDowideit use can use where git to find the path on windows. Doesn't work in PowerShell though.
@dotnetCarpenter The PowerShell replacement for where git is (Get-Command git).Path