Closed ivanrlg closed 2 years ago
what is this output?
NavContainerHelper is version 0.6.5.7
NavContainerHelper is running as administrator
Host is Microsoft Windows 10 Enterprise - 2004
Docker Client Version is 19.03.8
Docker Server Version is 19.03.8
On the output I can see that you are running BcContainerHelper - do you also have NavContainerHelper installed? In that case you should uninstall that. I don't think that is the problem here though.
The problem is that the Get-BestGenericImageName returns an image which is newer than your host version and because of that, New-BcContainer uses HyperV isolation, which isn't installed on the machine.
I will fix this by never returning a generic image which is newer than the host OS. A new BcContainerHelper pre-release should be ready later today and you can test that.
You can also fix the issue by installing hyperv on the host machine.
Hello Freddy, sorry I forgot to remove this from your template
NavContainerHelper is version 0.6.5.7
NavContainerHelper is running as administrator
Host is Microsoft Windows 10 Enterprise - 2004
Docker Client Version is 19.03.8
Docker Server Version is 19.03.8
Actually this is configured to run to "Azure Devops" via the commit trigger and your CI.yml, I wouldn't know how to see the above information.
Then I would expect it to start working again when the next build of ContainerHelper is out.
fixed in 3.0.4
PLEASE DO NOT INCLUDE ANY PASSWORDS OR TOKENS IN YOUR ISSUE!!!
Describe the issue I'm using Azure Devops to build the unit tests, and recently I started getting the following error without making any changes to the settings:
DockerDo : docker: Error response from daemon: hcsshim::CreateComputeSystem ce024f4ac5f37b6b6a8966dc3b1a6a4f1d9e7fb2788c2b1dadf4bc289116f88d: The virtual machine could not be started because a required feature is not installed.
Scripts used to create container and cause the issue
Full output of scripts
Screenshots If applicable, add screenshots to help explain your problem.
Additional context
does it happen all the time? 2 weeks ago maybe it didn't happen.
did it use to work? No