Error with pre-create check: "This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory" even though it's enabled

docker devops
MrAkroMenToS picture MrAkroMenToS · Aug 10, 2019 · Viewed 10.6k times · Source

Running docker toolbox ( v19.03.1) from Windows 10 Home edition yields the following error message:

Running pre-create checks...
Error with pre-create check: "This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory"
Looks like something went wrong in step ´Checking if machine default exists´... Press any key to continue...

I tried a lot of help threads online, but all of them boils down to enabling AMD-V (or intel equivalent) in the BIOS (done), disabling Hyper-V (can't, Home edition doesn't even have it), disabling hypervisorlaunchtype (done) or disabling core isolation (it's off) and it still doesn't work. Here are some screenshots to show some of my settings.

Running a Ryzen 3600 with x570 board, I enabled virtualization in the BIOS:

Here is my bcdedit, hypervisorlaunchtype is Off.

Windows features: I tried all permutation of turning on and off virtual machine platform / windows hypervisor platform, none of them worked, this is the current state.

Core isolation off.

All settings in one image: Settings

I also tried disabling anti-virus, it didn't help. Tried reinstalling docker toolbox, VirtualBox, together, separately, didn't work. (tried VirtualBox versions 5.2.20 (included in docker toolbox installer) and the newest 6.0.10 version)

Any help is greatly appreciated!

Update: I successfully installed Ubuntu 18 (64 bit) in VirtualBox, so I assume my virtualization is perfectly fine, so the problem must be with Docker.

Answer

Mariusz picture Mariusz · Sep 18, 2019

I just faced same issue on Windows 10 Home with Docker Toolbox 18.09.3 (laptop powered by Ryzen 2500U): running normal linux image via Virtualbox works like a charm, and msinfo32 tool reports "virtualization enabled: true"

What helped me was adding --virtualbox-no-vtx-check to the docker-machine create command, to be more specific I used this cmd:

docker-machine create -d virtualbox --virtualbox-memory=4096 \
    --virtualbox-cpu-count=4 --virtualbox-disk-size=40960 \
    --virtualbox-no-vtx-check default

And everything worked just great! Hope this helps on your case as well :-)

Related questions

Using docker-compose to set containers timezones

I have a docker-compose file running a few Dockerfiles to create my containers. I don't want to edit my Dockerfiles to set timezones because they could change at any time by members of my team and I have a docker-compose.…

Read More
Update k8s ConfigMap or Secret without deleting the existing one

I've been using K8S ConfigMap and Secret to manage our properties. My design is pretty simple, that keeps properties files in a git repo and use build server such as Thoughtworks GO to automatically deploy them to be ConfigMaps …

Read More
How can I change permission of mounted volumes in docker-compose.yml from the docker-compose.yml?

version: '2' services: web: build: context: ./ dockerfile: deploy/web.docker volumes: - ./:/var/www ports: - "8080:80" links: - app How can I change permission (chmod) /var/www automatically when docker-compose up -d --build?

Read More