-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Docker Toolbox on Win10 on AMD64 machine precheck failure #830
Comments
Bump - same issues here. |
Sadly, I'm facing the same issue. |
An update from my side: |
Same issue. Microsoft Windows [Version 10.0.17763.253] 64-bit Installed the latest Docker Tools today. I already have VirtualBox 6 installed and it works without issue. I tried to run Quickstart and it failed with the above message, even though virtualization is most definitely enabled. |
As a side issue Windows 10 Home 64bit I found that even though Hyper-V was disabled in the windows features that it was enabled and therefore blocked Virtualbox from seeing that Virtualisation was indeed turned on. This meant that Virtualbox would only allow 32bit VMs to be created. This was fixed by enabling the Hyper-V feature -> restart Disable Hyper-V feature and restart again. At this point I got back Virtualbox and the ability to create 64bit VMs. |
same issue |
Same issue here |
@makro2400 suggestion of downgrading to "18.03.0-ce" worked for me. FYI I tried downloading the latest "18.09.3" at the time of my issue. And I am using Windows 10 Home and the AMD Ryzen threadripper 1950x. |
Had the same issue with my new AMD Ryzen laptop. I got the following error message:
Virtualization is enabled in my BIOS. Docker toolbox was working on my AMD Ryzen laptop last year. I can create a virtual machine with Virtualbox outside of Docker Toolbox on this laptop. I installed an older version of Docker Toolbox (18.06.1-ce) and it is now working. I believe this to be an issue with the way Docker Toolbox does the pre-flight check for virtualization, rather than a issue with the PC and Virtualbox. I suspect this is specific to AMD processors and maybe specific to their Ryzen line. |
Hello, I have just been trying the latest toolbox(v19.03.1) and kept failing for the same "AMD-v" reason and also for v18.09.3. But as soon as I tried the 18.03.0-ce version it worked. |
Same issue here (Ryzen 5 2500U). Latest working version is 18.03.0-ce... |
Same behaviour, 18.03.0-ce works. 3900x, Win 10 |
Try running
|
Same behaviour on Ryzen 2400G, works with 18.03.0-ce but not with the latest version. |
I have an old AMD a6-3430mx so ofc I have same problem and same solution. I think that it's windows's problem 'cause I have familiar problem with android studio. |
Same issue, ryzen 2600. |
Same issue, Ryzen 9 3950, downgrade to specified version worked. |
The same issue, solved by running as suggested by @gudang Docker Version: 19.03.5 |
Probably relates to #166 |
Same problem here. Running the command : docker-machine create -d virtualbox --virtualbox-memory=2048 --virtualbox-no-vtx-check default will install the docker vm however I am unable to connect to it.. If I run docker ps, I get an error. When is a fix coming? |
Same problem here. Win 10 home |
@tessierp try setting the environment variables again |
Not working for latest AMD processor (I am using Docker Toolbox - is using VB 5.2.xx)
I manually installed VB 6.1.4 r136177, create guest OS's were working perfectly fine. I have in office old Intel i7, docker toolbox was working fine. |
@altyne Any chance you could provide the steps you used to make this work? It is still failing for me. |
@tessierp Its not working. What I mean what is working was install VBOX directly and create vm it will create successfully. But thru docker.exe creating vm (internally it using VBOX infrastructure), it fails during pre-checks "This computer doesn't have VT-X/AMD-v enabled....." So the bug is the pre-checker for docker itself. |
First, try removing After that, running again command: |
Same issue, ryzen 2400G on DockerToolbox-19.03.1 |
Same issue, AMD 3950X on DockerToolbox-19.03.1, Windows 10 Enterprise LTSC 1809 |
Expected behavior: Docker Quickstart Terminal would successfully start Docker CLI.
Actual behavior: Docker Quickstart Terminal indicates startup failure with error message:
Information
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: