Closed PaulFurlet closed 2 years ago
It looks like something went wrong during generation of filesonly generic images in december, so when you had the latest windows update on your host, it couldn't find a matching generic image and reverted to hyperv isolation (which you do not have installed on your machine).
The Generic image should be in place now, you can retry. If you install hyperv, then this won't fail next time, instead it will just use hyperv.
There might always be a window from the time where people upgrade their host computer and until generic images are in place (not many weeks:-)), therefore I always suggest that people have hyperv installed.
@freddydk Thank you for the answer. These are virtual machines with Windows Server 2019 Datacenter (2016 Datacenter where older docker is) created in Azure, they have Hyper-V installed by default. I will try to remove docker image with -filesonly name, probably it will recreate it and go correct next time.
Not necessary - you can just re-run now, the new image is there.
on Hyperv - the error above is: [Event Detail: Cannot start Hyper-V Container '5d9970c207ec5289de5b85f69a2b9ed3a551042826a5dbfbc9753ec86892f150' since the hypervisor is not running in the host.
Which lead me to assume that something is not running.
but again - the new generic image is there and should be auto-pulled.
@freddydk Thanks, all went smoothly this time.
Hello @freddydk!
I've got the same error today.
BcContainerHelper is version 3.0.1
BcContainerHelper is running as administrator
Host is Microsoft Windows Server 2016 Standard - ltsc2016
Docker Client Version is 20.10.5
Docker Server Version is 20.10.5
Removing bc from container hosts file
Removing bc-* from container hosts file
Removing C:\ProgramData\BcContainerHelper\Extensions\bc
Fetching all docker images
Fetching all docker volumes
Using image mcr.microsoft.com/businesscentral:10.0.14393.4886
Creating Container bc
Style: sandbox
Multitenant: No
Version: 20.0.35891.0
Platform: 20.0.35749.0
Generic Tag: 1.0.2.1
Container OS Version: 10.0.14393.4886 (ltsc2016)
Host OS Version: 10.0.14393.4889 (ltsc2016)
Using hyperv isolation
Using locale en-US
Disabling the standard eventlog dump to container log every 2 seconds (use -dumpEventLog to enable)
Downloading C:\ProgramData\BcContainerHelper\Extensions\bc\Microsoft.VisualStudio.Services.VSIXPackage.vsix
Using license file C:\agent\_work\1\s\Scripts\DevOps\TestSanaOnDailyBCBuild\Lic\lic.flf
Files in C:\ProgramData\BcContainerHelper\Extensions\bc\my:
- AdditionalOutput.ps1
- license.flf
- MainLoop.ps1
- SetupNavUsers.ps1
- SetupVariables.ps1
- updatehosts.ps1
Creating container bc from image mcr.microsoft.com/businesscentral:10.0.14393.4886
2a31bf6a7c408d985cd48ea7e23977a808602a2ab3723cd3600b326c2412a613
New-BcContainer Telemetry Correlation Id: 38caba1f-ca4b-446a-b670-7eaeb4440032
DockerDo : docker: Error response from daemon: hcsshim::CreateComputeSystem
2a31bf6a7c408d985cd48ea7e23977a808602a2ab3723cd3600b326c2412a613: No hypervisor is present on this system.
[Event Detail: Cannot start Hyper-V Container '2a31bf6a7c408d985cd48ea7e23977a808602a2ab3723cd3600b326c2412a613' since
the hypervisor is not running in the host. Provider: 17103e3f-3c6e-4677-bb17-3b267eb5be57 EventID: 12001]
(extra info: {"SystemType":"Container","Name":"2a31bf6a7c408d985cd48ea7e23977a808602a2ab3723cd3600b326c2412a613","Owner
":"docker","IgnoreFlushesDuringBoot":true,"LayerFolderPath":"C:\\ProgramData\\docker\\windowsfilter\\2a31bf6a7c408d985c
d48ea7e23977a808602a2ab3723cd3600b326c2412a613","Layers":[{"ID":"922160b9-8c7c-5f2f-acbc-e37eee66539c","Path":"C:\\Prog
Could you provide me with troubleshooting steps here, please?
Hello @freddydk!
I've got the same error today.
BcContainerHelper is version 3.0.1 BcContainerHelper is running as administrator Host is Microsoft Windows Server 2016 Standard - ltsc2016 Docker Client Version is 20.10.5 Docker Server Version is 20.10.5 Removing bc from container hosts file Removing bc-* from container hosts file Removing C:\ProgramData\BcContainerHelper\Extensions\bc Fetching all docker images Fetching all docker volumes Using image mcr.microsoft.com/businesscentral:10.0.14393.4886 Creating Container bc Style: sandbox Multitenant: No Version: 20.0.35891.0 Platform: 20.0.35749.0 Generic Tag: 1.0.2.1 Container OS Version: 10.0.14393.4886 (ltsc2016) Host OS Version: 10.0.14393.4889 (ltsc2016) Using hyperv isolation Using locale en-US Disabling the standard eventlog dump to container log every 2 seconds (use -dumpEventLog to enable) Downloading C:\ProgramData\BcContainerHelper\Extensions\bc\Microsoft.VisualStudio.Services.VSIXPackage.vsix Using license file C:\agent\_work\1\s\Scripts\DevOps\TestSanaOnDailyBCBuild\Lic\lic.flf Files in C:\ProgramData\BcContainerHelper\Extensions\bc\my: - AdditionalOutput.ps1 - license.flf - MainLoop.ps1 - SetupNavUsers.ps1 - SetupVariables.ps1 - updatehosts.ps1 Creating container bc from image mcr.microsoft.com/businesscentral:10.0.14393.4886 2a31bf6a7c408d985cd48ea7e23977a808602a2ab3723cd3600b326c2412a613 New-BcContainer Telemetry Correlation Id: 38caba1f-ca4b-446a-b670-7eaeb4440032 DockerDo : docker: Error response from daemon: hcsshim::CreateComputeSystem 2a31bf6a7c408d985cd48ea7e23977a808602a2ab3723cd3600b326c2412a613: No hypervisor is present on this system. [Event Detail: Cannot start Hyper-V Container '2a31bf6a7c408d985cd48ea7e23977a808602a2ab3723cd3600b326c2412a613' since the hypervisor is not running in the host. Provider: 17103e3f-3c6e-4677-bb17-3b267eb5be57 EventID: 12001] (extra info: {"SystemType":"Container","Name":"2a31bf6a7c408d985cd48ea7e23977a808602a2ab3723cd3600b326c2412a613","Owner ":"docker","IgnoreFlushesDuringBoot":true,"LayerFolderPath":"C:\\ProgramData\\docker\\windowsfilter\\2a31bf6a7c408d985c d48ea7e23977a808602a2ab3723cd3600b326c2412a613","Layers":[{"ID":"922160b9-8c7c-5f2f-acbc-e37eee66539c","Path":"C:\\Prog
Could you provide me with troubleshooting steps here, please?
@freddydk freddydk I removed KB5010790 and now everything works fine on 14393.4886 build. Please check what's affects container in 14393.4889.
The problem occurs when your host computer is upgraded before the corresponding generic images have been shipped. BcContainerHelper will default to HyperV isolation if host OS doesn't match container OS (for Windows Server 2016, Windows Server 2019 and Windows 10). Since your computer doesn't have hyperv installed, it fails. There isn't much I can do about that. If you install hyperv on the machine, it won't fail next time. The generic images for February Windows Updates should be out today.
I have similar issue.
I have similar issue.
I read through this issue and i still haven't solved problem.
Describe the issue I have three VMs that used to run validation normally before 2022 started. Now Run-ALValidation gives error "Unexpected error while validating app. Error is: docker: Error response from daemon: hcsshim::CreateComputeSystem c0c5f8a5663af945832 f70524872b0d292d622bd6270deb5f9d1b6bebf302f97: The virtual machine could not be started because a required feature is not installed. ExitCode: 125"
One of the VMs has older version of the Docker, there error is a bit more meaningful: "Unexpected error while validating app. Error is: docker.exe: Error response from daemon: CreateComputeSystem 5d9970c207ec5289de5b85f69a2b9ed3a551042826a5dbfbc9753ec86892f150: No hyperv isor is present on this system. [Event Detail: Cannot start Hyper-V Container '5d9970c207ec5289de5b85f69a2b9ed3a551042826a5dbfbc9753ec86892f150' since the hypervisor is not running in the host. Provider: 17103e3f-3c6 e-4677-bb17-3b267eb5be57 EventID: 12001]"
Creating new BC Container is running successfully. I use the following script for new container:
Scripts used to create container and cause the issue
Full output of scripts
Older docker version output:
Screenshots none applicable
Additional context