Skip to content

Task/azure pipeline#27

Closed
dewitt4 wants to merge 3 commits into
mainfrom
task/azure-pipeline
Closed

Task/azure pipeline#27
dewitt4 wants to merge 3 commits into
mainfrom
task/azure-pipeline

Conversation

@dewitt4

@dewitt4 dewitt4 commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

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.

Co-Authored-By: Claude Opus 4.8 noreply@anthropic.com

dewitt4 added 2 commits June 20, 2026 15:34
…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.
@dewitt4 dewitt4 self-assigned this Jun 22, 2026
@dewitt4 dewitt4 added the bug Something isn't working label Jun 22, 2026
@dewitt4 dewitt4 closed this Jun 23, 2026
@dewitt4
dewitt4 deleted the task/azure-pipeline branch June 23, 2026 02:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant