Choosing Right Size for Windows 10 VM in Azure to Run Docker

The post “Setup Windows 10 VM in Azure to Develop with Docker CE” has a detailed walkthrough on setting up Docker CE in Azure VM, which is using Windows 10. While trying out the same, encountered an issue to start the Docker giving error message “Failed to start the virtual machine 'MobyLinuxVM' because one of the Hyper-V components is not running. 'MobyLinuxVM' failed to start.” It is interesting to inspect and find a fix to this issue.

The full error message was as shown below.

Failed to start the virtual machine 'MobyLinuxVM' because one of the Hyper-V components is not running.

'MobyLinuxVM' failed to start. (Virtual machine ID xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx)

The Virtual Machine Management Service failed to start the virtual machine 'MobyLinuxVM' because one of the Hyper-V components is not running (Virtual machine ID 8CDE6654-DC88-4810-AB14-C1779F05B167).
at Start-MobyLinuxVM, <No file>: line 300
at <ScriptBlock>, <No file>: line 395
    at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeClient.cs:line 36
    at Docker.Actions.DoStart(SynchronizationContext syncCtx, Boolean showWelcomeWindow, Boolean executeAfterStartCleanup) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 77
    at Docker.Actions.<>c__DisplayClass16_0.<Start>b__0() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 61
    at Docker.WPF.TaskQueue.<>c__DisplayClass19_0.<.ctor>b__1() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.WPF\TaskQueue.cs:line 59

Inspecting the log also does provide only above error details.

Hyper-v is enabled in the machine as per instructions in “Setup Windows 10 VM in Azure to Develop with Docker CE”.

The GitHub issue discussed here helped to get an idea on the needs and when check whether CPU virtualization enabled in task manager, noticed it was not enabled.

Wrong size is selected for the VM might have caused issue was the guess. Checked nested virtualization enabled VM sizes for Azure here. The size of VM selected was not a nested virtualization supported size.

Changed size to v3 which is supporting nested virtualization.

Yay! now the virtualization is enabled.

Docker is running fine.