Closed Arthurvdv closed 2 years ago
Fixed in next release (this week)
v1.449: ALOpsDockerCreate: OS Detection for Windows Server 2019 (2022)
Thanks, will check next week and report back.
*** Artifact Url: [https://bcartifacts.azureedge.net/sandbox/20.1.39764.41349/w1]
*** Build new Image based on [https://bcartifacts.azureedge.net/sandbox/20.1.39764.41349/w1]
*** Artifact Type : [sandbox]
*** Artifact Version: [20.1.39764.41349]
*** Artifact Country: [w1]
*** OS: [2022]
*** OS version: [10.0.20348.707]
*** Image Template: [%IMAGE_PREFIX%:%ARTIFACT_TYPE%-%ARTIFACT_VERSION%-%ARTIFACT_COUNTRY%-%OS_VERSION%-%OS_LTSC%]
*** ImageName: [myimage:sandbox-20.1.39764.41349-w1-10.0.20348.707-ltsc2022]
and
mcr.microsoft.com/businesscentral:10.0.20348.707
Generic Tag: 1.0.2.7
Container OS Version: 10.0.20348.707 (ltsc2022)
Host OS Version: 10.0.20348.707 (ltsc2022)
Using process isolation
The detection of the OS and process isolation seems to be working, thanks!
Describe the bug We're in the process of setting up new BuildServers with based on Windows Server 2022 Standard (21H1), to replace the current the BuildServers with Windows Server 2019 Standard.
The goal here is to have Process isoloation working as intended. Combined with the "PowerShell way" of installing Docker.
(credits @Freddydk)
the used yaml
the output Also the complete output is necessary for us to see what is going on. Also use backtics:
Expected behavior Detecting the right OS version (and not thrown an warning)
Screenshots
Additional context It's a VM to test this version of Windows, our other BuildServers are physically machines.