Windows Docker Toolbox won't start - windows

Attempting to start up Docker Toolbox 1.12.0 on Windows 10 and getting the following error
Running pre-create checks...
Creating machine...
(default) Copying C:\Users\abc\.docker\machine\cache\boot2docker.iso to C:\Users\abc\.docker\machine\machines\default\boot2docker.iso...
(default) Creating VirtualBox VM...
(default) Creating SSH key...
Error creating machine: Error in driver during machine creation: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe createvm --basefolder C:\Users\abc\.docker\machine\machines\default --name default --register failed:
VBoxManage.exe: error: Code REGDB_E_IIDNOTREG (0x80040155) - Interface not registered (extended info not available)
VBoxManage.exe: error: Context: "CreateMachine(bstrSettingsFile.raw(), bstrName.raw(), ComSafeArrayAsInParam(groups), bstrOsTypeId.raw(), createFlags.raw(), machine.asOutParam())" at line 272 of file VBoxManageMisc.cpp
Looks like something went wrong in step ´Checking if machine default exists´... Press any key to continue...
Has anyone encountered this error before?

Re-installing VirtualBox and then restarting my machine fixed the problem. Hopefully this fixes yours too.

You can solve this problem by reinstalling VirtualBox, and choosing repair mode.
C:\Program Files\Docker Toolbox\installers\virtualbox -> virtualbox.exe.
After finishing the process, restart you machine and smile!

Related

Failed to create the VirtualBox object

I was trying to login into the already existing vm using vagrant in bash. But it says failed to start or it's not running.
This is a already existing vm in the local.
I tried
$vagrant global-status -> to get the vm id.
then,
$vagrant up <id> ->to start the vm.
Got the following error,
There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["showvminfo", "cd2ec772-3e94-476f-a0d9-59c3d2768fb5"]
Stderr: VBoxManage.exe: error: Failed to create the VirtualBox object!
VBoxManage.exe: error: Code REGDB_E_CLASSNOTREG (0x80040154) - Class not registered (extended info not available)
VBoxManage.exe: error: Most likely, the VirtualBox COM server is not running or failed to start.

Starting minikube on Windows 7 fails to start with - Error getting state for host: machine does not exist

Have been trying to setup Kubernetes for local development on my Windows 7 machine with a VirtualBox VM Driver. Installing and running minikube fails each time with the below error:
D:\minikube>minikube start --vm-driver=virtualbox
Starting local Kubernetes v1.9.0 cluster...
Starting VM...
E0219 09:47:24.441727 4220 start.go:159] Error starting host: Error getting state for host: machine does not exist.
Retrying.
E0219 09:47:24.448727 4220 start.go:165] Error starting host: Error getting state for host: machine does not exist
E0219 09:47:54.448727 4220 util.go:151] Error uploading error message: :
Post https://clouderrorreporting.googleapis.com/v1beta1/projects/k8s-minikube/events:report?key=AIzaSyACUwzG0dEPcl-eOgpDKnyKoUFgHdfoFuA: dial tcp 172.217.25.138:443: i/o timeout
I suspected this may be happening due to minikube cache downloading at a network drive folder (N:) due to enterprise configurations in my laptop, however, copying the .minikube folder from N:\.minikube to C:\Users\abc123\.minikube has not abated the problem.
Do let me know if someone has managed to solve it.
I ran into the same error on osx after re-installing minikube. Simply deleting the minikube VM and restarting fixed everything:
$ minikube delete
$ minikube start
Go to C:\Users\\
Delete the .minikube folder
Start minikube (minikube.exe start --kubernetes-version="v1.10.0" --vm-driver="virtualbox")
Try using powershell/cygwin instead of cmd.
Also delete .minikube folder
do minikube delete
then minikube start
In certain scenarios, it may be an issue with your VM driver. If you don't specify one, it may default to VirtualBox. But if you have HyperV instead (due to installing docker on windows, for example) then it won't start. You may have to start it like so:
minikube start --vm-driver hyperv
Or whatever is appropriate.

OpenStack training-labs - VBoxManage.exe: error: Invalid machine group

I am trying to install OpenStack instance into VirtualBox VMs as on https://wiki.openstack.org/wiki/Documentation/training-labs#Building_the_cluster
after ./osbash.sh -w cluster I get error
VBoxManage.exe: error: Invalid machine group 'C:/Program Files/Git/labs'
Yes, C:/Program Files/Git is location of git-bash.exe that is actual Git-Windows Bash, but how to make osbash.sh proceed with correct machine group name?
The scripts are stable Mitaka from http://docs.openstack.org/training_labs/ for Windows
http://tarballs.openstack.org/training-labs/dist/labs-stable-mitaka.zip
Paul#aspire MINGW64 /d/Workspaces/OpenStack/labs-stable-mitaka/labs/osbash
$ ./osbash.sh -b cluster
Base disk: base-ssh-mitaka-ubuntu-14.04-server-amd64
Distribution name: ubuntu
Virtualization provider: virtualbox
Creating Windows batch scripts: no
Creating cluster on this machine: yes
VM access method: ssh
GUI type: headless
2016年09月20日 18:09:36 osbash starting
Creating basedisk.
2016年09月20日 18:09:36 osbash vm_install starts.
Asked to delete VM "base" (not found)
Creating VM "base"
VBoxManage.exe: error: Invalid machine group 'C:/Program Files/Git/labs'
VBoxManage.exe: error: Details: code E_INVALIDARG (0x80070057), component VirtualBoxWrap, interface IVirtualBox, callee IUnknown
VBoxManage.exe: error: Context: "ComposeMachineFilename(bstrName.raw(), bstrPrimaryGroup.raw(), createFlags.raw(), bstrBaseFolder.raw(), bstrSettingsFile.asOutParam())" at line 264 of file VBoxManageMisc.cpp
FAILURE: VBoxManage: createvm --name base --register --ostype Ubuntu_64 --groups /labs
P.S. The same error when trying the latest master from git://git.openstack.org/openstack/training-labs.git
Raised bug https://bugs.launchpad.net/labs/+bug/1625562
The documentation may have mislead you. You don't need a POSIX environment to build the cluster on Windows and (as you found out) using the bash scripts does not work on Windows.
All you need is a VirtualBox installation and the content of the zip file you downloaded. There is no need to add VBoxManage to the Path, the scripts should find the executable anyway.
The zip file you downloaded contains the Windows batch files that build the cluster on Windows in the wbatch directory. Just double-click them: 1) create_hostnet 2) create_base 3) create_ubuntu_cluster_node
That's all. The scripts will set up the VMs, download the Ubuntu ISO image and build the OpenStack cluster.

Docker Quickstart Terminal fails to start VirtualBox VM in Windows 10

I've tried several times to start the Docker VM via the Docker Quickstart Terminal. After deleting the default virtual machine in VirtualBox I receive the following output
Creating Machine default...
Running pre-create checks...
Creating machine...
(default) OUT | Creating VirtualBox VM...
(default) OUT | Creating SSH key...
(default) OUT | Starting VirtualBox VM...
Error creating machine: Error in driver during machine creation: exit status 1
Looks like something went wrong... Press any key to continue...
To troubleshoot further, I attempted to start the default machine in the VirtualBox GUI directly using Start > Headless Start, as suggested in other Docker issues. The startup failed and I received an error dialog box with the content:
Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).
Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).
Result Code:
E_FAIL (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Versions of related components:
VirtualBox Version 5.0.11 r104393
Docker Toolbox 1.9.1a
Windows 10 Version 1511 (OS Build 10586.14)
One of the answers to this question solved my problem. Here it is with a few edits:
I found a solution
Open Windows Network Connections
Right click on VirtualBox Host only adapter that was created
Choose properties
Check "VirtualBox NDIS6 Bridged Networking driver"
Disable and Enable the highlighted item
For me "VirtualBox NDIS6 Bridged Networking Driver" was not checked. I checked it and clicked OK to close the Properties window. After that, the Docker Quickstart Terminal was able to start the VM successfully.
The same thing happened to me. At this moment I am using Windows Home.
At least in my case, what happened was that the environment variables DOCKER_MACHINE and DOCKER_TOOLBOX_INSTALL_PATH were not created for the system.
I just had to add them and it worked.
I tried to follow #chris-hunt answer, but I didn't found the highlighted item. I realized it was due to the fact I didn't installed the VirtualBOX that comes in the Docket Tools installation. I think I was using an older version.
So I uninstalled docker tools AND VitualBOX, both on windows Control Panel. After that, I reinstalled Docker Tools with the VirtualBOX checked, and it finally worked.

Restoring Laravel's Homestead after critical error

I'm using Homestead via Vagrant for my Laravel environment. When I ran vagrant up today, there was a critical error saying that the box is inaccessible.
One of the instructions that I found on the web suggested unregistering the VM by using its machine uuid, which I did:
> VBoxManage.exe unregistervm [uuid]
After unregistering the status of Homestead box changed from inaccessible to not created.
Next step was to register the box, which I do like this:
> VBoxManage.exe registervm "C:\Users\Rhino\VirtualBox VMs\homestead\box-disk1.vmdk"
However the command above throws the following error:
VBoxManage.exe: error: Start tag expected, '<' not found.
VBoxManage.exe: error: Location: 'C:\Users\Rhino\VirtualBox VMs\homestead\box-disk1.vmdk', line 1 (0), column 1.
What am I doing wrong?
OK, I figured it out. There was probably a step missing in the guide I found - creation. All the steps again:
(1)Unregister the box with machine uuid. The uuid can be found e.g. in the .vbox-prev file in your homestead virtual machine folder. Run this when you retrieve the uuid:
C:\Program Files\Oracle\VirtualBox> VBoxManage.exe unregistervm [uuid]
(2)Create the box with --register flag:
C:\Program Files\Oracle\VirtualBox> VBoxManage.exe createvm --name "C:\Users\Rhino\VirtualBox VMs\homestead\box-disk1.vmdk" --register
(3)Delete the folder in which your homestead vm is kept (I guess it's by default created in VirtualBox VMs folder)
(4)Run vagrant up

Resources