[release/10.0] Switch Linux container hosts from Ubuntu to Azure Linux 3 #122166
Conversation
github-actions
bot
added
the
needs-area-label
Co-authored-by: richlander <[email protected]>
Co-authored-by: richlander <[email protected]>
|
@copilot Please also update x64/amd64 and Arm32 as well. Our Arm32 runs are executed on Arm64 hosts. I didn't realize that there were some x64 VMs still left to change. |
There was a problem hiding this comment.
Pull request overview
This PR migrates Arm64 Linux container hosts from Ubuntu 22.04 to Azure Linux 3 across CI/CD pipeline configurations. The change affects only container host VMs (the host that runs the container), while bare VMs and the container images themselves remain unchanged.
Key changes:
- Updates 7 container host entries across 3 YAML configuration files
- Changes format from
Ubuntu.2204.ArmArch[.Open]toAzureLinux.3.Arm64[.Open]for the container host specification - Affects both public and internal configurations for
linux_arm64andlinux_musl_arm64(Alpine) platforms
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
eng/pipelines/coreclr/templates/helix-queues-setup.yml |
Updates 4 container host entries for linux_arm64 and linux_musl_arm64 platforms (both public and internal configurations) |
eng/pipelines/libraries/helix-queues-setup.yml |
Updates 2 container host entries for linux_arm64 and linux_musl_arm64 platforms; also corrects lowercase 'open' to 'Open' in one entry |
eng/pipelines/installer/helix-queues-setup.yml |
Updates 1 container host entry for linux_musl_arm64 platform |
Updated in commit ec96025. All x64/amd64 and Arm32 container hosts using Ubuntu have been switched to Azure Linux 3: Changes made:
Note: WASM/Browser platforms (wasi_wasm, browser_wasm, browser_wasm_firefox) still use Ubuntu.2204.Amd64 as container hosts, matching the current main branch. Let me know if these should also be updated. |
|
@copilot Please update WASM/Browser hosts as well. I missed those by accident. |
Co-authored-by: richlander <[email protected]>
Updated in commit 1230b3a. WASM/Browser container hosts have been switched to Azure Linux 3:
Note: browser_wasm in coreclr was already using AzureLinux.3.Amd64.Open. |
jkotas
removed
the
needs-area-label
jkotas
changed the title
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
|
These errors all seems unrelated and affecting image types that were not affected by this change. |
|
/ba-g "Unrelated failures" |
|
Using tell mode for this infra change. |
main PR
Description
Updated all helix-queues-setup.yml files to migrate Linux VMs from Ubuntu 22.04/24.04 to Azure Linux 3 when used as container hosts. Bare VMs without container relationships remain unchanged.
Changes across three files:
eng/pipelines/coreclr/templates/helix-queues-setup.yml: 12 container host entrieseng/pipelines/installer/helix-queues-setup.yml: 2 container host entrieseng/pipelines/libraries/helix-queues-setup.yml: 7 container host entriesAffected platforms:
linux_arm64: Both public and internal configurationslinux_musl_arm64(Alpine): Both public and internal configurationslinux_arm(Arm32): Both public and internal configurationslinux_musl_x64(Alpine x64): Both public and internal configurationslinux_musl_arm(Alpine Arm32): Both public and internal configurationswasi_wasm: WASM/Browser platformbrowser_wasm: WASM/Browser platformbrowser_wasm_firefox: WASM/Browser Firefox platformFormat changes:
(Container)Ubuntu.2204.ArmArch[.Open]@image→(Container)AzureLinux.3.Arm64[.Open]@image(Container)Ubuntu.2204.Amd64[.Open]@image→(Container)AzureLinux.3.Amd64[.Open]@imageNote: Arm32 containers run on Arm64 hosts, hence they use AzureLinux.3.Arm64 as the container host.
Customer Impact
No direct customer impact. Infrastructure-only change to align testing infrastructure with current platform standards.
Regression
Not applicable. Infrastructure configuration update only.
Testing
Changes are declarative YAML configuration. Validation performed by comparing against main branch patterns and verifying all container host references are updated consistently across all architectures including WASM/Browser platforms.
Risk
Low. Changes only affect CI/CD infrastructure configuration for container host selection. Container images and test workloads remain unchanged. Pattern matches existing main branch implementation.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.