You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 26, 2021. It is now read-only.
AMD FX-8370 Eight-Core Processor
Windows 10 Pro Version 1803 (Build 17134.753)
Docker version 18.09.3, build 774a1f4eee
VBoxManage Version 6.0.6r130049
I see there was some changes regarding VT-X detection in the recent release.
by any change did this break something?
I'm honestly not sure how to roll back the software as I kinda just updated on a whim (my fault).
Playing around with docker-toolbox at the moment and attempting to recreate my "default" machine seems to be giving me some grief...
$ docker-machine create default
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"
I attempted to look for related issues regarding this and really saw nothing that would help; (So my apologize if I'm duplicating) some peoples examples had issues with "nested virtualization" and that doesn't fit my case as I'm just running toolbox on bare-metal windows.
The text was updated successfully, but these errors were encountered:
AMD FX-8370 Eight-Core Processor
Windows 10 Pro Version 1803 (Build 17134.753)
Docker version 18.09.3, build 774a1f4eee
VBoxManage Version 6.0.6r130049
I see there was some changes regarding VT-X detection in the recent release.
by any change did this break something?
I'm honestly not sure how to roll back the software as I kinda just updated on a whim (my fault).
Playing around with docker-toolbox at the moment and attempting to recreate my "default" machine seems to be giving me some grief...
I attempted to look for related issues regarding this and really saw nothing that would help; (So my apologize if I'm duplicating) some peoples examples had issues with "nested virtualization" and that doesn't fit my case as I'm just running toolbox on bare-metal windows.
The text was updated successfully, but these errors were encountered: