Task/azure pipeline#27
Closed
dewitt4 wants to merge 3 commits into
Closed
Conversation
…tion Add postgresLocation param to main.bicep (defaults to location so prod is unaffected) and override it to eastus2 in the staging parameter file. All other staging resources remain in eastus.
…Node 20 The supply-chain hardening switched the container base images to MCR, but mcr.microsoft.com/cbl-mariner/base/nodejs:20 does not exist — the CBL-Mariner 2.0 Node.js repo only publishes up to Node 18, so `az acr build` failed at the FROM step with "manifest tagged by 20 is not found". Azure Linux 3.0 is the successor to CBL-Mariner and publishes the runtimes we need: azurelinux/base/nodejs:20 and azurelinux/base/python:3.12. It's the same distro family (tdnf, groupadd/useradd), so the existing Dockerfile bodies and Azure Artifacts feed wiring carry over unchanged. - core, frontend: cbl-mariner/base/nodejs:20 -> azurelinux/base/nodejs:20 - ai-service: cbl-mariner/base/python:3.12 -> azurelinux/base/python:3.12 Keeps the MCR-hosted, Microsoft-built provenance from the hardening work rather than reverting to Docker Hub images. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> fix: use Azure Linux base images instead of non-existent CBL-Mariner Node 20 The supply-chain hardening switched the container base images to MCR, but mcr.microsoft.com/cbl-mariner/base/nodejs:20 does not exist — the CBL-Mariner 2.0 Node.js repo only publishes up to Node 18, so `az acr build` failed at the FROM step with "manifest tagged by 20 is not found". Azure Linux 3.0 is the successor to CBL-Mariner and publishes the runtimes we need: azurelinux/base/nodejs:20 and azurelinux/base/python:3.12. It's the same distro family (tdnf, groupadd/useradd), so the existing Dockerfile bodies and Azure Artifacts feed wiring carry over unchanged. - core, frontend: cbl-mariner/base/nodejs:20 -> azurelinux/base/nodejs:20 - ai-service: cbl-mariner/base/python:3.12 -> azurelinux/base/python:3.12 Keeps the MCR-hosted, Microsoft-built provenance from the hardening work rather than reverting to Docker Hub images.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fix: use Azure Linux base images instead of non-existent CBL-Mariner Node 20
The supply-chain hardening switched the container base images to MCR, but
mcr.microsoft.com/cbl-mariner/base/nodejs:20 does not exist — the CBL-Mariner
2.0 Node.js repo only publishes up to Node 18, so
az acr buildfailed at theFROM step with "manifest tagged by 20 is not found".
Azure Linux 3.0 is the successor to CBL-Mariner and publishes the runtimes we
need: azurelinux/base/nodejs:20 and azurelinux/base/python:3.12. It's the same
distro family (tdnf, groupadd/useradd), so the existing Dockerfile bodies and
Azure Artifacts feed wiring carry over unchanged.
Keeps the MCR-hosted, Microsoft-built provenance from the hardening work
rather than reverting to Docker Hub images.
Co-Authored-By: Claude Opus 4.8 noreply@anthropic.com