Docker installation on new hardware (Windows 10 Pro 1903)

I bought a new notebook and I can’t install Docker on it. I followed the same procedure I used on the old PC:

1.Enable bios virtualization technology and install only Docker Toolbox;
2.Disable hyper-v;
3.Install the latest version of VirtualBox;
4.Remove all Docker folders from “ProgramData” at each attempt;
5.Starting Kitematic (Alpha);
6.Starting Docker Quickstart Terminal;
I can’t run point 5, I can’t create the default virtual machine in virtualbox. I have Windows 10 1903. I get this error message:

Command failed: C:\Program Files\Docker Toolbox\docker-machine.exe -D create -d virtualbox --virtualbox-memory 2048 default,Docker Machine Version: 0.16.1, build cce350d7,Found binary path at C:\Program Files\Docker Toolbox\docker-machine.exe,Launching plugin server for driver virtualbox,Plugin server listening at address 127.0.0.1:49941,() Calling .GetVersion,Using API Version 1,() Calling .SetConfigRaw,() Calling .GetMachineName,(flag-lookup) Calling .GetMachineName,(flag-lookup) Calling .DriverName,(flag-lookup) Calling .GetCreateFlags,Found binary path at C:\Program Files\Docker Toolbox\docker-machine.exe,Launching plugin server for driver virtualbox,Plugin server listening at address 127.0.0.1:49943,() Calling .GetVersion,Using API Version 1,() Calling .SetConfigRaw,() Calling .GetMachineName,(default) Calling .GetMachineName,(default) Calling .DriverName,(default) Calling .GetCreateFlags,(default) Calling .SetConfigFromFlags,Reading certificate data from C:\Users\HP 255 G7\.docker\machine\certs\ca.pem,Decoding PEM data...,Parsing certificate...,Reading certificate data from C:\Users\HP 255 G7\.docker\machine\certs\cert.pem,Decoding PEM data...,Parsing certificate...,(default) Calling .PreCreateCheck,(default) DBG | COMMAND: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe --version,(default) DBG | STDOUT:,(default) DBG | {,(default) DBG | 5.2.20r125813,(default) DBG | },(default) DBG | STDERR:,(default) DBG | {,(default) DBG | },(default) DBG | Hyper-V is not installed.,Error with pre-create check: "This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory",open C:\Users\HP 255 G7\.docker\machine\machines\default\default\Logs\VBox.log: Impossibile trovare il percorso specificato.,notifying bugsnag: [Error with pre-create check: "This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory"],

Note well:

1.Enable bios virtualization technology …;

This computer doesn’t have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory

!?!?!?!?!

I cite from the page about Docker Toolbox: ‘Legacy desktop solution. Docker Toolbox is for older Mac and Windows systems that do not meet the requirements of Docker Desktop for Mac and Docker Desktop for Windows. We recommend updating to the newer applications, if possible.’
This means you went in the wrong direction already at point 1.

Everything is written on this page but it doesn’t work for me!


I can’t use Docker but Docker Toolbox because I have to have VirtualBox running.

I tried again now but I get the usual errors. I’m sorry but Docker on Windows doesn’t work!

Among the rest also classic Docker, what you advise does not work. I report the errors I get. Docker on Windows doesn’t work, it has a lot of bugs and malfunctions.

Unable to start: Il comando in esecuzione è stato interrotto perché la variabile di preferenza “ErrorActionPreference” o il parametro comune è impostato su Stop: Impossibile avviare ‘MobyLinuxVM’.

Impossibile avviare la macchina virtuale ‘MobyLinuxVM’ perché uno dei componenti di Hyper-V non è in esecuzione.

Impossibile avviare ‘MobyLinuxVM’. (ID macchina virtuale F26D29AB-EADC-43E4-BFB1-2EF0B2BC32E4)

Servizio Virtual Machine Management: impossibile avviare la macchina virtuale ‘MobyLinuxVM’ perché uno dei componenti di Hyper-V non è in esecuzione (ID macchina virtuale F26D29AB-EADC-43E4-BFB1-2EF0B2BC32E4).
in Start-MobyLinuxVM, : riga 296
in , : riga 412
in Docker.Core.Pipe.NamedPipeClient.Send(String action, Object parameters) in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeClient.cs:riga 36
in Docker.Actions.DoStart(SynchronizationContext syncCtx, Boolean showWelcomeWindow, Boolean executeAfterStartCleanup) in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:riga 92
in Docker.Actions.<>c__DisplayClass19_0.b__0() in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:riga 74
in Docker.WPF.TaskQueue.<>c__DisplayClass19_0.<.ctor>b__1() in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.WPF\TaskQueue.cs:riga 59

Since 6.0.0 Virtualbox can use Hyper-V as an execution core, see the changelog.

Docker Toolbox has a lot of issues, that’s why it was replaced with Desktop. If new issues arise around Win 10 1903 I’m sure nobody is going to fix them.
Docker Desktop on the other hand works, I use it 7 days a week, on 1903 too.

1 Like

Docker Toolbox
In my tests I tried both versions of VirtualBox, both the most recent version and the older one. I always have mistakes. Docker Toolbox does not work.

Docker Desktop
I installed this program and it doesn’t work, I don’t invent lies (above you find the errors I get). Docker Desktop does not work.

I have to use VirtualBox so I will never use the Desktop version but only the Toolbox version. Yours is a case like mine. A program to be a good product must work on all computers and not just a few. On my desktop computer I have an older version of Windows 10 and Docker Toolbox works perfectly. A new version of Docker Toolbox must be published otherwise I will abandon this program. Maybe Docker Toolbox doesn’t work on laptop.

Does VirtualBox work for you? I had a problem with Windows Sandbox activated. I had to run
bcdedit /set hypervisorlaunchtype off
in PowerShell (or cmd) as an admin and then restart computer. IMO WSB enables Hyper-V for itself to work, I don’t know exactly, I wasn’t digging into it what was the problem. For me weren’t working apps like VirtualBox and VMWare Workstation.

Command failed: C:\Program Files\Docker Toolbox\docker-machine.exe -D create -d virtualbox --virtualbox-memory 2048 default,Docker Machine Version: 0.16.1, build cce350d7,Found binary path at C:\Program Files\Docker Toolbox\docker-machine.exe,Launching plugin server for driver virtualbox,Plugin server listening at address 127.0.0.1:49856,() Calling .GetVersion,Using API Version 1,() Calling .SetConfigRaw,() Calling .GetMachineName,(flag-lookup) Calling .GetMachineName,(flag-lookup) Calling .DriverName,(flag-lookup) Calling .GetCreateFlags,Found binary path at C:\Program Files\Docker Toolbox\docker-machine.exe,Launching plugin server for driver virtualbox,Plugin server listening at address 127.0.0.1:49858,() Calling .GetVersion,Using API Version 1,() Calling .SetConfigRaw,() Calling .GetMachineName,(default) Calling .GetMachineName,(default) Calling .DriverName,(default) Calling .GetCreateFlags,(default) Calling .SetConfigFromFlags,Reading certificate data from C:\Users\EB-Virtualbox\.docker\machine\certs\ca.pem,Decoding PEM data...,Parsing certificate...,Reading certificate data from C:\Users\EB-Virtualbox\.docker\machine\certs\cert.pem,Decoding PEM data...,Parsing certificate...,(default) Calling .PreCreateCheck,(default) DBG | COMMAND: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe --version,(default) DBG | STDOUT:,(default) DBG | {,(default) DBG | 6.0.10r132072,(default) DBG | },(default) DBG | STDERR:,(default) DBG | {,(default) DBG | },(default) DBG | Hyper-V is not installed.,Error with pre-create check: "This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory",open C:\Users\EB-Virtualbox\.docker\machine\machines\default\default\Logs\VBox.log: Impossibile trovare il percorso specificato.,notifying bugsnag: [Error with pre-create check: "This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory"],

I don’t see any changes. Something bad happens while Docker Toolbox creates the virtual operating system on VirtualBox.

I followed this procedure:

1 - I run Windows prompt as an administrator;
2 - Enter your string;

Microsoft Windows [Versione 10.0.18362.239]
(c) 2019 Microsoft Corporation. Tutti i diritti sono riservati.
C:\WINDOWS\system32>bcdedit /set hypervisorlaunchtype off
Operazione completata.
C:\WINDOWS\system32>

3 - Restart the PC;
4 - I install “DockerToolbox-18.09.3.exe”;

This is 99% problem with misconfiguration on your PC. That error is produced by VBox, not Docker Toolbox.

Let’s try something. Open C:\Windows\System32\OptionalFeatures.exe (just paste it into search bar on taskbar) and post screenshot of all enabled / disabled things.

Maybe I understood your concern. You think I haven’t enabled virtualization from the BIOS and that I haven’t disabled the Hyper-V program from OptionalFeatures.exe. In reality these two specifications are the first two things I did.
Thank you very much for your help and your availability.

This might be a stupid question. but you said you have enabled it in BIOS. What exactly? In my BIOS is VT-d, VT-X and so on, like more things about virtualization. Are you sure you have the right thing?

In the bios I read:
“Virtualization Technology”
and there are 2 options:
“Enable”
“Disabled”
I chose “Enable” obviously. The notebook is a recent HP product, like CPU I have a Ryzen 2200U.
I don’t read “VT-d, VT-X” in the BIOS.

It does work for me. I installed it several months ago, I could double check that it is still working with latest patches/updates.
Something that you should verify is that the Hypervisor can be started and viewed. This is unrelated to docker and any Windows Hyper-V VM could run in it. This helped me realize that Docker (on Windows) is using a different virtualization technology than on Linux.

See also

Hopefully one of these things will help diagnose the problem.

No, I can’t use Docker Desktop because I need VirtualBox. I have to use Docker Tolbook.

If Docker Toolbox v18.09.4 is not released, Docker becomes a service that works only on Apple and Linux but not Windows.

I don’t believe that only on my notebook with Windows 10 Pro 1903, Docker doesn’t work. In my opinion it is a problem for many. Maybe you’ve updated to 1903 with Docker already installed.

In the bios I read:
“Virtualization Technology”
and there are 2 options:
“Enable”
“Disabled”
I chose “Enable” obviously. The notebook is a recent HP product, like CPU I have a Ryzen 2200U.
I don’t read “VT-d, VT-X” in the BIOS.

Sorry for late response. Please try what’s answered here

How can I tell if my CPU (Ryzen 2200U) is compatible with Docker?