Description
The newest Windows docker image for ltsc2025 (mcr.microsoft.com/windows/servercore:ltsc2025) is too new to run on the windows-2025 runner image and so fails with the following error:
docker: Error response from daemon: container [sha] encountered an error during hcs::System::Start: failure in a Windows system call: The virtual machine or container exited unexpectedly. (0xc0370106).
As far as I can find, this is because the host (runner image) has an older OS version than the container image and so can't run it. The host kernel version must be equal to or newer than the Docker image. The runner full version is 10.0.26100.2894 while the recently updated ltsc2025 container is 10.0.26100.3194. The container image was updated in the last few days because we have successful builds from ~5 days ago that are failing today.
On a related note (since it is relevant for Windows containers), it would be helpful if the "Set up job" step printed the "full" version (including the "Update Build Revision") and not just 10.0.26100 in the "Operation System" details.
Platforms affected
Runner images affected
Image version and build link
Is it regression?
no
Expected behavior
The mcr.microsoft.com/windows/servercore:ltsc2025 should run (e.g., via docker build or docker run).
Successful docker image (from a build ~5 days ago):
mcr.microsoft.com/windows/servercore:ltsc2025@sha256:f6153b44882e7ada8fa17123cfca1da3f29ea7fbe062c9e931240dc837aa4256
- created date from image config:
2025-01-13T03:08:16.9200244Z
"os.version": "10.0.26100.2894"
$ $Version = Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion"
$ echo "Version $($Version.ReleaseId) (OS Build $ $($Version.CurrentMajorVersionNumber).$($Version.CurrentMinorVersionNumber).$($Version.CurrentBuildNumber).$($Version.UBR))"
Version 2009 (OS Build 10.0.26100.2894)
$ docker run -i --rm mcr.microsoft.com/windows/servercore:ltsc2025@sha256:f6153b44882e7ada8fa17123cfca1da3f29ea7fbe062c9e931240dc837aa4256 powershell -command '$Version = Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion"; echo "Version $($Version.ReleaseId) (OS Build $($Version.CurrentMajorVersionNumber).$($Version.CurrentMinorVersionNumber).$($Version.CurrentBuildNumber).$($Version.UBR))"'
Version 2009 (OS Build 10.0.26100.2894)
Actual behavior
Failing docker image:
mcr.microsoft.com/windows/servercore:ltsc2025 (sha256:44b2884c5db9f03d57b7494371706cf95d4345c75399c420e63b5f5609313ee6)
- created date from image config:
2025-02-08T22:54:28.3301623Z
"os.version": "10.0.26100.3194"
$ $Version = Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion"
$ echo "Version $($Version.ReleaseId) (OS Build $ $($Version.CurrentMajorVersionNumber).$($Version.CurrentMinorVersionNumber).$($Version.CurrentBuildNumber).$($Version.UBR))"
Version 2009 (OS Build 10.0.26100.2894)
$ docker run -i --rm mcr.microsoft.com/windows/servercore:ltsc2025 powershell -command '$Version = Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion"; echo "Version $($Version.ReleaseId) (OS Build $($Version.CurrentMajorVersionNumber).$($Version.CurrentMinorVersionNumber).$($Version.CurrentBuildNumber).$($Version.UBR))"'
docker: Error response from daemon: container c5ace0ad02bb10d19a82b1543d1c0e11086f2b3c6da9715bca407ff450cf535d encountered an error during hcs::System::Start: failure in a Windows system call: The virtual machine or container exited unexpectedly. (0xc0370106).
Error: Process completed with exit code 1.
Repro steps
runs-on: windows-2025
steps:
- run: |
docker run -i --rm mcr.microsoft.com/windows/servercore:ltsc2025 cmd /c ver
Description
The newest Windows docker image for ltsc2025 (
mcr.microsoft.com/windows/servercore:ltsc2025) is too new to run on thewindows-2025runner image and so fails with the following error:docker: Error response from daemon: container [sha] encountered an error during hcs::System::Start: failure in a Windows system call: The virtual machine or container exited unexpectedly. (0xc0370106).As far as I can find, this is because the host (runner image) has an older OS version than the container image and so can't run it. The host kernel version must be equal to or newer than the Docker image. The runner full version is
10.0.26100.2894while the recently updatedltsc2025container is10.0.26100.3194. The container image was updated in the last few days because we have successful builds from ~5 days ago that are failing today.On a related note (since it is relevant for Windows containers), it would be helpful if the "Set up job" step printed the "full" version (including the "Update Build Revision") and not just
10.0.26100in the "Operation System" details.Platforms affected
Runner images affected
Image version and build link
docker run)docker build)docker build)Is it regression?
no
Expected behavior
The
mcr.microsoft.com/windows/servercore:ltsc2025should run (e.g., viadocker buildordocker run).Successful docker image (from a build ~5 days ago):
mcr.microsoft.com/windows/servercore:ltsc2025@sha256:f6153b44882e7ada8fa17123cfca1da3f29ea7fbe062c9e931240dc837aa42562025-01-13T03:08:16.9200244Z"os.version": "10.0.26100.2894"Actual behavior
Failing docker image:
mcr.microsoft.com/windows/servercore:ltsc2025(sha256:44b2884c5db9f03d57b7494371706cf95d4345c75399c420e63b5f5609313ee6)2025-02-08T22:54:28.3301623Z"os.version": "10.0.26100.3194"Repro steps