chore(deps): update runc-containerd-minor (minor)

[renovate]

This PR contains the following updates:

Package	Update	Change
moby-runc	minor	1.4.3-ubuntu24.04u1 → 1.5.0-ubuntu24.04u1
moby-runc	minor	1.4.3-ubuntu22.04u1 → 1.5.0-ubuntu22.04u1
moby-runc	minor	1.4.1-ubuntu20.04u1 → 1.5.0-ubuntu20.04u1

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[aks-node-assistant]

AgentBaker Linux gate detective

Run: https://msazure.visualstudio.com/CloudNativeCompute/_build/results?buildId=169093190
Failed job/stage/task: e2e / Run AgentBaker E2E
Summary: E2E failed after Ubuntu2004 FIPS nodes became Ready, but validation pods never reached Running. The default and scriptless_nbc variants retried 300s pod waits and ended with context deadline exceeded / client rate limiter errors.

Likely cause/signature: recurring shared-cluster/pod-readiness fleet issue (shared-cluster-fleet-outage, repair item #38373323). Confidence: Medium-high.
Alternative considered: the runc/containerd component bump broke pod startup; less likely because image lookup and node readiness succeeded, the symptoms match the active shared-cluster repair signature, and PR #8758 only changes component metadata.
Recommended owner/action: No PR action; E2E/shared-cluster owners should continue repair item #38373323.
Wiki: https://dev.azure.com/msazure/09706533-03bf-4b43-9a9b-b49c75429646/_wiki/wikis/ed4a85e9-1085-4151-a39b-2753523eba2b?pagePath=%2FAKS%2FSIGs%20and%20Teams%2FAKS%20Components%2FSIG%3A%20Node%20Lifecycle%2FAI%20Agent%20Knowledge%2FAgentBaker%20Gate%20PR%20Pipeline%20Flakiness (shared-cluster-fleet-outage)

[aks-node-assistant]

AgentBaker Linux gate detective

Run: https://msazure.visualstudio.com/CloudNativeCompute/_build/results?buildId=169119640
Failed job/stage/task: e2e / Run AgentBaker E2E
Summary: E2E failed on the known stale NetworkIsolated shared-cluster issue. abe2e-azure-networkisolated-v3-d6cc9 was already Deleting / Failed; NetworkIsolated scenarios failed in get or create cluster with cluster ... is in state Failed, won't retry. Missing SIG-image skips and later CSE/pod timeouts are secondary noise.

Likely cause/signature: shared NetworkIsolated cluster cleanup corruption (networkisolated-shared-cluster-delete-blocked-inuse-nsg, repair #38506740). Confidence: High.
Alternative considered: PR #8758's runc/containerd metadata bump; less likely because the failure is shared cluster lifecycle before scenario-specific validation and PR only changes components.json.
Recommended owner/action: No PR action; E2E infra owner should clean/quarantine stale NetworkIsolated resources and continue repair #38506740.
Wiki: https://dev.azure.com/msazure/09706533-03bf-4b43-9a9b-b49c75429646/_wiki/wikis/ed4a85e9-1085-4151-a39b-2753523eba2b?pagePath=%2FAKS%2FSIGs%20and%20Teams%2FAKS%20Components%2FSIG%3A%20Node%20Lifecycle%2FAI%20Agent%20Knowledge%2FAgentBaker%20Gate%20PR%20Pipeline%20Flakiness (networkisolated-shared-cluster-delete-blocked-inuse-nsg)

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[aks-node-assistant]

AgentBaker Linux gate detective

Run: https://msazure.visualstudio.com/CloudNativeCompute/_build/results?buildId=169154232
Failed job/stage/task: e2e / Run AgentBaker E2E
Summary: E2E failed on the known NetworkIsolated shared-cluster cleanup blockage. abe2e-azure-networkisolated-v3-d6cc9 was in Failed/deleting state, and deletion failed with ResourceGroupDeletionBlocked / InUseNetworkSecurityGroupCannotBeDeleted because abe2e-networkisolated-securityGroup is still attached to the shared VNET subnet.

Likely cause/signature: stale NetworkIsolated shared cluster NSG in-use (networkisolated-shared-cluster-delete-blocked-inuse-nsg, repair #38506740). Confidence: High.
Alternative considered: PR #8758's runc/containerd metadata bump; less likely because the failure is shared cluster deletion/NSG cleanup and PR only changes components.json.
Recommended owner/action: No PR action; E2E infra owner should resolve the NSG/subnet association and continue repair #38506740.
Wiki: https://dev.azure.com/msazure/09706533-03bf-4b43-9a9b-b49c75429646/_wiki/wikis/ed4a85e9-1085-4151-a39b-2753523eba2b?pagePath=%2FAKS%2FSIGs%20and%20Teams%2FAKS%20Components%2FSIG%3A%20Node%20Lifecycle%2FAI%20Agent%20Knowledge%2FAgentBaker%20Gate%20PR%20Pipeline%20Flakiness (networkisolated-shared-cluster-delete-blocked-inuse-nsg)

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[aks-node-assistant]

Failed gate run

Run: https://msazure.visualstudio.com/CloudNativeCompute/_build/results?buildId=169443002
Failed job/stage/task: e2e / Run AgentBaker E2E / Run AgentBaker E2E

Detective summary

Test_Ubuntu2204_HTTPSProxy_PrivateDNS/scriptless_nbc failed during VMSS CSE provisioning before kubelet started. Timeline and build status both show Run AgentBaker E2E failed with exit code 1; the E2E log shows CustomScript ExitCode=50, KubeletStartTime=n/a, and the known mandb/oldlocal pattern.

Likely cause and signature

Known recurring CSE/provisioning flake rather than a runc/containerd PR regression. Signature: ubuntu2204-httpsproxy-privatedns-cse-exit50-outbound-kubelet-na. Confidence: high. Strongest alternative: the runtime version bump caused provisioning failure, but the same signature predates this run and is already linked to repair Bug #38559852.

Recommended owner/action

Node Lifecycle repair owner should continue Bug #38559852; no PR author action is indicated from this evidence.

Evidence

• Task log: logId 538; job log: logId 545
• Wiki signature: ubuntu2204-httpsproxy-privatedns-cse-exit50-outbound-kubelet-na
• Repair item: https://msazure.visualstudio.com/CloudNativeCompute/_workitems/edit/38559852

[aks-node-assistant]

Failed gate run

Run: https://msazure.visualstudio.com/CloudNativeCompute/_build/results?buildId=169455329
Failed job/stage/task: e2e / Run AgentBaker E2E / Run AgentBaker E2E; plus build / build2404gen2containerd / Test, Scan, and Cleanup

Detective summary

E2E first failed in Test_Ubuntu2204_HTTPSProxy_PrivateDNS/scriptless_nbc: VM validation reached validators.go:1010, then localdns-exporter@...service unexpectedly entered failed state. Timeline and build status both corroborate the E2E task exit code 1. The VHD scan also reported known CIS rule 6.1.4.1|pass->fail in build2404gen2containerd; the scan script exited 0 but emitted a CIS regression issue.

Likely cause and signature

E2E: recurring LocalDNS exporter unit-state flake, now escalated to repair Bug #38581800. Signature: localdns-exporter-systemd-failed-state. Confidence: medium-high. Strongest alternative: the runc/containerd bump destabilized node services, but this signature already recurred across unrelated builds. CIS: known Ubuntu 24.04 Gen2 containerd CIS compliance signal under repair Bug #38529622. Signature: linux-vhd-prgate-cis-ubuntu2404-gen2-containerd-6141-pass-fail. Confidence: high.

Recommended owner/action

Node Lifecycle E2E/LocalDNS owners should inspect failed localdns-exporter@...service logs across the affected builds. Linux VHD/CIS owners should continue the existing CIS repair investigation; no PR-specific action is indicated from this evidence alone.

Evidence

• E2E task log: logId 538; job log: logId 545
• CIS task log: logId 445; CIS report: cis-report-169455329-1782367064673.html
• Wiki signatures: localdns-exporter-systemd-failed-state, linux-vhd-prgate-cis-ubuntu2404-gen2-containerd-6141-pass-fail
• Repair items: https://msazure.visualstudio.com/CloudNativeCompute/_workitems/edit/38581800 and https://msazure.visualstudio.com/CloudNativeCompute/_workitems/edit/38529622

[Copilot]

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.