The virtual machine could not be started because a required feature is not installed...

Bruce Gust
Bruce Gust used Ask the Experts™
on
Trying to run Docker and I'm getting this error:

$ bash bin/development.sh
Building express-mongoose-es6-rest-api
Step 1/9 : FROM node:8.10.0
 ---> 41a1f5b81103
Step 2/9 : MAINTAINER Kunal Kapadia <kunalkapadia12@gmail.com>
Service 'express-mongoose-es6-rest-api' failed to build: failed to start service utility VM (createreadwrite): hcsshim::CreateComputeSystem 7be3d4b1e2c0b1026873e49e7b782f851fde4296ed082a0942ddee02bbb9f688_svm: The virtual machine could not be started because a required feature is not installed.
(extra info: {"SystemType":"container","Name":"7be3d4b1e2c0b1026873e49e7b782f851fde4296ed082a0942ddee02bbb9f688_svm","Layers":null,"HvPartition":true,"HvRuntime":{"ImagePath":"C:\\Program Files\\Linux Containers","LinuxInitrdFile":"initrd.img","LinuxKernelFile":"kernel"},"ContainerType":"linux","TerminateOnLastHandleClosed":true})

When I'm looking at that, I'm seeing what I have in bold. I'm google-ing this stuff now, but if there's anybody out there who's been down this road who can tell me what I need to do to make this work, I'm all ears!

Thanks!
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Technical Lead - Network Security
Commented:
I found this comment:

I had the same error message. I was running docker on an Azure vm. Though it did work for a while on a B4ms, it started showing the error after a few reboots. I changed it to a D2_v3 to fix the issue. (I found the solution here: https://blog.darrenjrobinson.com/azure-vm-docker-createcontainer-error-0xc0370102/)

It seems like it should help you out
Bruce GustPHP Developer

Author

Commented:
Nathan!

This could very well be what I'm looking for in that I'm running Parallels on a Mac.

I read through the article and I got lost when it started talking about:

Changing my VM Size from a DS_v2 to a DS_v3 was all that I had to do. My Docker Containers are now running on a Windows 10 Virtual Machine in Azure Resource Manager.

What is the equivalent to that on a Parallels system?
Philip ElderTechnical Architect - HA/Compute/Storage
Commented:
It sounds like it is running nested within a virtual machine that is already a guest hosted in a hypervisor on a host?

If that's the case, then the host hypervisor needs to support virtualization pass-through to the guest so that it can pick up and run.
Nathan HawkinsTechnical Lead - Network Security

Commented:
So in Azure you can select VM's based on the kind of performance you need so a DS is a D-Series VM, and they went from version 2 to version 3 within the D-Series sets of VMs.

I am going to agree with Philip. This appears to be a doubly hosted VM. So Parallels is a Virtual Desktop emulation for windows on a MAC. SO in the emulation are you running something like Virtualbox or VMWare with Docker installed in a VM there (or something of that equivalent)? If so then there's some driver issues going on. A potential problem could be Virtualization pass through, but IMO...You are running too much emulation. You have emulated drivers trying to emulate a Virtual Machine. It just sounds clugey.
Bruce GustPHP Developer

Author

Commented:
Gentlemen!

I got it figured out!

I had to go into Parallels and enable nested emulators. Once that was in place, we were gold!

Thanks!

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial