Fix Hyper-V sandbox image for Windows Server 2025 compatibility#557
Conversation
|
Hi @rzlink. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Tip We noticed you've done this a few times! Consider joining the org to skip this step and gain Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
de96bab to
e6f8909
Compare
The VHD marketplace images bake pause:3.10 (or 3.10.1) as the containerd sandbox_image, but these versions lack a Windows Server 2025 manifest. On Server 2025 hosts with Hyper-V isolation, this causes containerd to boot a Server 2022 UVM from the pause image while selecting Server 2025 app image layers (based on host OS), resulting in HCS_E_IMAGE_MISMATCH when mounting 2025 layers inside the 2022 UVM. This fix patches the containerd config to use pause:3.10.2 (which includes Server 2025 variant) during Windows node provisioning when HYPERV=true. It also pre-pulls the image since the VHD only ships with older pause versions. pause:3.10.2 is backward-compatible — it includes all platform variants from pause:3.10 plus Server 2025 (26100.6899).
e6f8909 to
68fba5f
Compare
|
/test |
|
/test all |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rzlink, zylxjtu The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/ok-to-test |
|
/hold cancel |
The VHD marketplace images bake pause:3.10 (or 3.10.1) as the containerd sandbox_image, but these versions lack a Windows Server 2025 manifest. On Server 2025 hosts with Hyper-V isolation, this causes containerd to boot a Server 2022 UVM from the pause image while selecting Server 2025 app image layers (based on host OS), resulting in HCS_E_IMAGE_MISMATCH when mounting 2025 layers inside the 2022 UVM.
This fix patches the containerd config to use pause:3.10.2 (which includes Server 2025 variant) during Windows node provisioning when HYPERV=true. It also pre-pulls the image since the VHD only ships with older pause versions.
pause:3.10.2 is backward-compatible — it includes all platform variants from pause:3.10 plus Server 2025 (26100.6899).