Closed sauerkreut closed 8 months ago
It tries to use HyperV isolation, because it states that HyperV is enabled - but it looks like HyperV is not working. If you update your host machine with the latest windows update, then it should work. I will investigate if I can default to process isolation in this case (for the next version).
We are using vmImage: 'Windows-Latest' ( https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml#software ). So I am very limited with windows updates.
Got it - try to insert this line after loading BcContainerHelper:
$bcContainerHelperConfig.defaultNewContainerParameters = @{ "isolation" = "Process" }
Hey @freddydk We are experiencing the same issues in our AL-go for github this morning. Can we add the same parameter there is a way or what to do there? Thanks
I will ship a fix for this in containerhelper asap.
Should be working again in approx. 1 hour
PS: Oops, you closed it.
Ltsc2019 is also being chosen for Windows 10, HyperV not installed.
2024-03-14T07:25:04.1226600Z Generic Tag: 1.0.2.17
2024-03-14T07:25:04.1630572Z Container OS Version: 10.0.17763.5576 (ltsc2019)
2024-03-14T07:25:04.1645309Z Host OS Version: 10.0.19045.4170 (22H2)
2024-03-14T07:25:04.1701450Z WARNING: Host OS and Base Image Container OS doesn't match and process isolation is specified. If you encounter issues, you could try to specify -isolation hyperv
2024-03-14T07:25:04.1709749Z Using process isolation
2024-03-14T07:26:37.1143303Z Step 5/6 : RUN \Run\start.ps1 -installOnly -multitenant -includeTestToolkit -includeTestLibrariesOnly
2024-03-14T07:26:37.3328832Z ---> Running in 82225614aff6
2024-03-14T07:26:40.4013128Z DockerDo : hcs::CreateComputeSystem 82225614aff6b80974637bd17d8556a3a9486501ceba3d3735105199e0600956: The container
2024-03-14T07:26:40.4014374Z operating system does not match the host operating system.
2024-03-14T07:26:40.4014716Z ExitCode: 1
2024-03-14T07:26:40.4016360Z Commandline: docker build --isolation=process --memory 8G --no-cache --tag navimage:daily-gb.4
2024-03-14T07:26:40.4017087Z c:\bcartifacts.cache\yzxzhwh5.yym
2024-03-14T07:26:40.4018958Z At C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\6.0.9\ContainerHandling\New-NavImage.ps1:715 char:27
2024-03-14T07:26:40.4020790Z + ... if (!(DockerDo -command build -parameters @("--isolation=$isola ...
2024-03-14T07:26:40.4021305Z + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2024-03-14T07:26:40.4021925Z + CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
2024-03-14T07:26:40.4022526Z + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,DockerDo
2024-03-14T07:26:40.4023071Z
2024-03-14T07:26:40.4984930Z ##[error]PowerShell exited with code '1'.
@rdebath - it was closed with the checkin (even though the version isn't shipped yet) On Windows 10 - there are no supported Container OS' for Windows 10 - we will have to use Windows Server 2019 with HyperV isolation. Sorry, but there is nothing I can do about that. Today, you can still point out the generic image (version 1.0.2.15) which still exists - but after March 25th - they will be gone.
I might document how people can build the generic image themselves if they are running in a configuration like this - I am just not sure whether the old "hack" of running the 20H2 container will work much longer - that will likely be removed as well.
Hi @freddydk thanks for the quick fix!
Will you be creating an official release today or will the fix only be available in the preview for now?
@freddydk ah i see that you created the release. Thank you!
PLEASE DO NOT INCLUDE ANY PASSWORDS OR TOKENS IN YOUR ISSUE!!!
Describe the issue Running a pipeline after the "Fairly big change rolling out on Business Central on Docker!!!" by Freddy Kristiansen on Yammer ( https://www.yammer.com/dynamicsnavdev/#/Threads/show?threadId=2707513621381120 ) returns: ##[error]DockerDo : docker: Error response from daemon: hcs::CreateComputeSystem 20a2d6b76d69c179ca2b39b2969833e015b9f6aa998cac334ea47601cae371dd: The virtual machine could not be started because a required feature is not installed. ExitCode: 125
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