Reputation: 392
I am going through the documentation on Docker Get Started (Part 4), and one of the first steps there is to create a VM using VirtualBox. now I've met all prerequisites and have everything set up, but this step fails on error message
Creating CA: /home/tadeasbucha/.docker/machine/certs/ca.pem
Creating client certificate: /home/tadeasbucha/.docker/machine/certs/cert.pem
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 don't have access to any hardware machine on which I could try this one. Is it possible to set up Azure VM (Ubuntu 16.04) to enable virtualization? I've also tried to disable the virtualization check when creating the VM, but in that case it's stuck on assigning IP address.
Upvotes: 6
Views: 18687
Reputation: 11
I think they've made changes recently.
Virtualization applications other than Hyper-V are not supported for nested virtualization. This includes any software that requires hardware virtualization extensions.
Upvotes: 0
Reputation: 41
In my case I was using a VM size that doesn't support Nested virtualization. I just had to use a size that supports it and, most importantly, set the Security Type to Standard (in the Basics section). Here is a list of D(s)v3 VMs that support Nested virtualization.
Upvotes: 4
Reputation: 359
D and E Knowing that it mattered what kind of VM you choose with respect to having virtualization enabled I created a Standard D8s v3 VM. But when trying to get Hyper-V setup with this script
Install-WindowsFeature Hyper-V, Containers
I got the error
Install-WindowsFeature : A prerequisite check for the Hyper-V feature failed.
1. Hyper-V cannot be installed because virtualization support is not enabled in the BIOS.
Thought it might be working when changing size to Standard D4s v3, but to no avail. Tried creating a new VM Standard D4s v3, but the same issue.
So, contrary to various internet resources mentioning that the v3 series VM should have virtualization enabled this clearly is not the case today - any longer? Would ove to learn what VM series do have vritualization enabled or how I could get it turned on on an Azure VM.
Upvotes: 1
Reputation: 41
In addition to Tadeáš Bucha's answer, you must choose Dv3, even the newer Dv4's do not work
Upvotes: 4
Reputation: 392
I was able to find a solution which is very easy and maybe I just didn't read the VM sizes description thoroughly. Because I had my VM on size Dv2, which unfortunately doesn't offer nested virtualization. When I increased the size of the VM to Dv3 (which apparently has the nested virtualization enabled by default with no further hassling inside of the VM), I was able to create the VMs inside of my VM with no issues.
Upvotes: 13