BUG : Unable to start the VM in docker toolbox

[nehalbhanushali]

Description

Steps to reproduce the issue:

1. Install Docker toolbox on Windows Home Edition
2. Open quickstart terminal

Describe the results you received:

Error creating machine: Error in driver during machine creation: Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm default --type headless failed:
VBoxManage.exe: error: The virtual machine 'default' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\nehal\.docker\machine\machines\default\default\Logs\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

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

Describe the results you expected:
Machine start

Additional information you deem important (e.g. issue happens only occasionally):
Was working fine until a week back

[karthiktrml]

I have the same issue with docker on Windows 10

Error

Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap
Interface:
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

docker-machine not running

C:\WINDOWS\system32> docker-machine ls
NAME ACTIVE DRIVER STATE U
default virtualbox Timeout

Unable to get it started

Starting "default"...
(default) Check network to re-create if needed...
(default) Windows might ask for the permission to create a network adapter. Sometimes, such confirmation window is minim
ized in the taskbar.
(default) Creating a new host-only adapter produced an error: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe hostonlyif create failed:
(default) 0%...
(default) Progress state: E_INVALIDARG
(default) VBoxManage.exe: error: Failed to create the host-only adapter
(default) VBoxManage.exe: error: Assertion failed: [!aInterfaceName.isEmpty()] at 'F:\tinderbox\win-5.1\src\VBox\Main\src-server\HostNetworkInterfaceImpl.cpp' (74) in long __cdecl HostNetworkInterfa
ce::init(class com::Bstr,class com::Bstr,class com::Guid,enum __MIDL___MIDL_itf_VirtualBox_0000_0000_0038).
(default) VBoxManage.exe: error: Please contact the product vendor!
(default) VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
(default) VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)" at line 94 of file VBoxManageHostonly.cpp
(default)
(default) This is a known VirtualBox bug. Let's try to recover anyway...
(default) Found a new host-only adapter: "VirtualBox Host-Only Ethernet Adapter #5"
(default) Windows might ask for the permission to configure a network adapter. Sometimes, such confirmation window is minimized in the taskbar.
(default) Windows might ask for the permission to configure a dhcp server. Sometimes, such confirmation window is minimized in the taskbar.
Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm default --type headless failed:

[nehalbhanushali]

VBoxHardening.log suggests reboot, but it still fails.

[karthiktrml]

@nehalbhanushali I think it might be the issue with Windows Hyper V according to our company IT guys. Can you check if your Hyper V is tuened on.

[AlexBondor]

A reboot after a fresh install of Docker Toolbox did the job for me!

[louiskareem]

UNINSTALL DOCKER TOOLBOX AND REINSTALL DOCKER TOOLBOX.
Don't forget to check "Install VirtualBox with NDIS5 driver" during toolbox installation.
That should do the trick.

[EMCP]

@louiskareem not seeing option to specify NDIS5 anywhere.. even installing vbox alone I don't see that option

[fjanon]

I added a new comment about this issue

#291

[BorislavKamenov]

Suggested by @louiskareem does the trick.
In Docker Toolbox Install Wizard there is a checkbox to use NDIS5 instead of default one NDIS6.
I've checked that and works.

[Higourang]

Running pre-create checks...
Error with pre-create check: "This computer is running Hyper-V. VirtualBox won't boot a 64bits VM when Hyper-V is activated. Either use Hyper-V as a driver, or disable the Hyper-V hypervisor. (To skip this check, use --virtualbox-no-vtx-check)"
Looks like something went wrong in step ´Checking if machine default exists´... Press any key to continue...

[Higourang]

[Higourang]

Finally I am resolve issue with docker on Windows 10, Docker Toolbox did the job for me!

[bhargavb7]

I'm having the same issue
"Error creating machine: Error in driver during machine creation: Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm default --type headless failed: VBoxManage.exe: error: The virtual machine 'default' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005)."
have tried reinstalling toolbox and used NDIS5 driver and still no luck. I have been trying to resolve this for the 2 days.

[joyang1]

@bhargavb7
have you fixed this issue?

[joyang1]

@Higourang
How do you solve this problem?
Can you say the solution?

[Higourang]

yes its fixed issue

…

On Sun, 16 Sep 2018, 11:19 Tommy Yang, ***@***.***> wrote: @Higourang <https://github.com/Higourang> How do you solve this problem? Can you say the solution? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#639 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AlUGuoykpfNDUoZQN-CzuxRPeSdEeInPks5ubeZrgaJpZM4M2iHE> .

[bhargavb7]

@Higourang I have checked my hyper-v is disabled and my virtualbox is updated and I have tried everything I found on the forums but still I think i'm kinda missing something. Can you help me out to resolve this issue??

[ahmedBou]

i have the same prob , i just let my ip adress public in windows firewall , go to windows firwall -> advanced setting ->inbound roule ->select new rule -> custom -> press next -> next -> add your ip adress -> press public

[badio93]

i have the same prob , i just let my ip adress public in windows firewall , go to windows firwall -> advanced setting ->inbound roule ->select new rule -> custom -> press next -> next -> add your ip adress -> press public

hello, citizen0x.
Sorry for the question, but i'm totally new to this kind of things...i'm here because of an installation i must do in order to simulate fluid effects on Rhino using OPENFOAM, on Windows10 system.

How your operation on firewall roules effects security on my system?
Moreover, when i should add my ip address, in which field i have to; local or remote?
Thanks a lot!

[tinomhishi]

Check if your processor is capable of virtualization.

[matematikom]

Hi, I am getting the same issue since a couple of months ago. Before that was working very good.
I am using Windows 10. Hyper-V is not active and I've tried with any version of Virtualbox (from 5.2.8 until recent 6).
Nothing was resolved trying to install VBox with NDIS5 driver.
Neither installing and rebooting or reinstalling and rebooting.
Has anyone solved the issu somehow?

[solarknight98]

i also meet this problem,how to solve it?

[Littlemen]

Installation of docker toolbox on windows 10 latest patch without installing Virtualbox led to errors.
I had permission errors on install and got a failed to open/create the internal network "name of the virtualbox adapter what ever it happens to be" (verr_intnet_flt_if_not_found)
I granted permissions to windows defender to run kitsmat.ext docker toolbox.exe docker machine.exe
and then started Docker Quickstart Terminal as administrator to fix this.
Took me hours of fiddling through the various posts.

[plalance]

I'm a bit late, but here is what i tried to make Docker work on Windows 10 Family (Build 1803 on my Acer Aspire V3 Laptop) :
The following concerns Docker usage via Docker Toolbox, it's only for this purpose and doesn't concerns Docker for Windows which works differently and needs Hyper-V, Windows 10 Pro version etc...

1 : Uninstall Virtualbox and delete .VirtualBox folder in C:/User/"Username" (important to erase old files from VB that could brick creation of VM via Docker Toolbox)

2 : Uninstall Docker Toolbox if you have already tried to install it AND delete ".docker" folder in C:/User/"Username".

3 : (Maybe and Surely Optionnal...) As i was very angry i ran CCleaner clean juste in case... ^^

4 : Launch Docker Toolbox via exe installator (without running as admin, just launch it normally it will ask you for permission in any case)
https://docs.docker.com/toolbox/overview/ (link to download .exe)

5 : During install process, please check all boxes (git, install Virtualbox etc...) AND please select "Custom" in install mode (top of the dialog box), selecting "Custom" will allow you to choose drivers in next step. Click next.

6: Please select NDIS5 version driver. Continue install to the end.

7: It should work, just launch Docker Quickstart terminal. And start enjoying Docker.

What didn't work for me :
1: Try to install Docker Toolbox without installing virtualbox at the ssame time. It looks like Docker Toolbox uses specifi version of VB and it's just recommanded to install THE VB that works with Docker TB...
2: Trying to launch VM manually... Trying to update VB manually... Trying to create Vhost only adapter manually...
3: Install Docker Toolbox with NDIS6 Drivers...
4: Launch in admin mode VB and/or docker quickstart terminal.

What my PC configuration is (this is my old laptop i decided to convert into small test machine and cluster for distributed / docker operations)
Windows 10 Family 1803 Build
I7-4702MQ 2.2GHZ
8gb Ram
Acer Aspire V3-772G laptop

Hope this will help, this is not a fully accepted solution as it forces you to remove / purge VB (and so forces you to backup potential Vms...).

If this doesn't help anyone, sorry for this.

[adist]

what if it is happened in ubuntu 18.04?? :7

[jkhaui]

@plalance I'm trying your fix now. Regardless of whether it ends up working, just wanted to say thanks for being one of the only people in the docker/windows forums who is capable of writing a coherent, logical & step-by-step answer

[asthagaur1]

Hello , I am also getting the same issue and tried all the above solution but not able to install.

[lucas625]

Hello guys, I had the same problem but combining the solution described by @plalance and a stackoverflow solution it worked just fine.

1. Follow the @plalance solution
2. On cmd as admin run: dism /Online /Disable-Feature:Microsoft-Hyper-V
3. Reboot
4. On cmd as admin run: bcdedit /set hypervisorlaunchtype off
5. Open docker quickstart.
   After these steps it should work.

[dieuhien1036]

lucas625: thank you so much ! you save my life T_T

[Arisdolanan]

This worked for me!! https://stackoverflow.com/questions/50053255/virtualbox-raw-mode-is-unavailable-courtesy-of-hyper-v-windows-10

[KinjalAkhani]

This worked for me!! https://stackoverflow.com/questions/50053255/virtualbox-raw-mode-is-unavailable-courtesy-of-hyper-v-windows-10

For me as well, Thanks !!

[cybermicheal47]

none worked

[harshfulzele987]

solution:
just enable your Hyper v and DHCP ,it really works :)

[Chhunneng]

This worked for me!! https://stackoverflow.com/questions/50053255/virtualbox-raw-mode-is-unavailable-courtesy-of-hyper-v-windows-10

Thank for it

[jigneshbutani]

Description

Steps to reproduce the issue:

1. Install Docker toolbox on Windows Home Edition
2. Open quickstart terminal

Describe the results you received:

Error creating machine: Error in driver during machine creation: Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm default --type headless failed:
VBoxManage.exe: error: The virtual machine 'default' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\nehal\.docker\machine\machines\default\default\Logs\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

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

Describe the results you expected:
Machine start

Additional information you deem important (e.g. issue happens only occasionally):
Was working fine until a week back

how to fix??

[plalance]

@jigneshbutani looks to my eyes like there is a driver issue or something like thath due to our favorite Microsoft OS and it's updates...

I recommend you the following :

Got to : to C:\Program Files\Oracle\VirtualBox\drivers\vboxdrv and then right-click on VBoxDrv.inf ==> install

Then : Open CMD prompt as admin and run "sc start vboxdrv"

Try to launch Docker / VB after process is complete...

Hope this will work for you...

[jhanif]

@plalance my docker is not working, any solution?

[jigneshbutani]

Dear Do DELET VM & RETRY SET UP you will definitely get tun. Jignesh Butani 9099285670

…

On Fri, Nov 6, 2020 at 10:01 AM jhanif ***@***.***> wrote: [image: image] <https://user-images.githubusercontent.com/52787258/98326325-8909d800-2023-11eb-9176-937389154c77.png> @plalance <https://github.com/plalance> my docker is not working, any solution? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#639 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARORZBTK6SH6EL4RCQ74WJ3SON32LANCNFSM4DG2EHCA> .

[jhanif]

@jigneshbutani It's not changing brother, any other solutions?

[jigneshbutani]

Try 2-3 times

…

On Fri, Nov 6, 2020 at 11:27 AM jhanif ***@***.***> wrote: @jigneshbutani <https://github.com/jigneshbutani> It's not changing brother, any other solutions? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#639 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARORZBQVWU5S4UABBKT4JWDSOOF4PANCNFSM4DG2EHCA> .

[jhanif]

@jigneshbutani still no working

[jigneshbutani]

I have solved this by deleting old VM and running new VM More on that cant

…

On Fri, Nov 6, 2020 at 11:35 AM jhanif ***@***.***> wrote: @jigneshbutani <https://github.com/jigneshbutani> still no working — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#639 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARORZBR7XMC5A3O7AKOJYPLSOOG2NANCNFSM4DG2EHCA> .

[jhanif]

@jigneshbutani do you have WA/Telegeam. I need your help.

[jigneshbutani]

no

…

On Fri, Nov 6, 2020 at 11:44 AM jhanif ***@***.***> wrote: @jigneshbutani <https://github.com/jigneshbutani> do you have WA/Telegeam. I need your help. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#639 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARORZBU5ZSCQUJRSVGDOYB3SOOH35ANCNFSM4DG2EHCA> .

[jhanif]

@jigneshbutani I already enable the hyper V, but it doesnt work

[jhanif]

@jigneshbutani
I already enable the hyper V. But it doesnt work.

[plalance]

Hi @jigneshbutani , I would not recommand to delete / create the VM... It produces the lost of all docker images / mounts / data in instances...
For me, this would be the ultimate solution if anithing other works...

[plalance]

@jhanif
Be careful jhanif, "Docker Toolbox" and "Docker for Windows" just don't work the same way at all.

What i recommand in my answers here, and previously (the past year) in this issue, were relying to Docker Toolbox.

Docker Toolbox (noawadays called Docker for Windows Home) does not required Hyper V to be activated, and as other people has already said , having Hyper V activated may prevent Docker Toolbox to work properly as it does not use this.

If you are running Docker Desktop (aka Docker for Windows 10 Pro / Enterprise / Student) you must activate Hyper V (and so, your computer / processor / OS must support it)

if you are running Docker for Windows Home (old Docker Toolbox), then it means your operating system is Windows 10 Family / Standard, and it means you don't have to use Hyper V.