fix: arm64 base digest #39

Merged
Noel merged 3 commits from fix/arm64-base-digest into main 2026-10-31 20:19:15 +00:00
4 changed files with 24 additions and 5 deletions
Showing only changes of commit 7981575f86 - Show all commits

No files matched your search

+7 -4
View File
@@ -12,11 +12,14 @@
# edits invalidate almost nothing.
#
# Base image is digest-pinned to the same node:26-slim digest as the dev
# container (OKF_Nuxt/decisions/dev-container-shape.md) - verified for the
# runner's arm64 and this workstation's x86_64.
# container (OKF_Nuxt/decisions/dev-container-shape.md). The digest is the
# multi-platform OCI INDEX, not a platform manifest: the previous pin was
# the linux/amd64 manifest digest, so `--platform linux/arm64` on the arm64
# runner failed instantly with "no matching manifest for linux/arm64".
# Index digest verified 2026-10-31 to contain linux/amd64 and linux/arm64/v8.
# syntax: no BuildKit-only features used, so the default frontend suffices.
FROM node:26-slim@sha256:18f03e4b532a63baf09809fe8349c2171807f1818cb6c5230fb12aecd5beda65 AS build
FROM node:26-slim@sha256:e4db4c914bf8ad241bd24804fc25d272d89bad97e68cdc8a1414862790a02c39 AS build
# pnpm pinned to the same version as CI (pr-checker.yml pins major 11) and
# the local toolchain (11.26.0). Installed via npm from the node image - no
@@ -38,7 +41,7 @@ COPY . .
RUN pnpm build
FROM node:26-slim@sha256:18f03e4b532a63baf09809fe8349c2171807f1818cb6c5230fb12aecd5beda65
FROM node:26-slim@sha256:e4db4c914bf8ad241bd24804fc25d272d89bad97e68cdc8a1414862790a02c39
# pnpm is NOT installed in the runtime image: nothing here runs pnpm.
ENV NODE_ENV=production \
+1 -1
View File
@@ -1,4 +1,4 @@
FROM node:26-slim@sha256:18f03e4b532a63baf09809fe8349c2171807f1818cb6c5230fb12aecd5beda65
FROM node:26-slim@sha256:e4db4c914bf8ad241bd24804fc25d272d89bad97e68cdc8a1414862790a02c39
# Node no longer bundles pnpm (corepack and pnpm are both absent from this
# image), so install it. First instruction, so later changes reuse the layer.
+11
View File
@@ -34,6 +34,17 @@ the gateway must now **proxy to this server** instead of embedding
`.output/public/`. That sibling decision needs updating; the compose wiring
is still open.
# The arm64 digest lesson (2026-10-31)
The first real release (`v1.5.0`, `v1.5.1`) failed at `Build image` after one
second: the pinned `sha256:18f03e4b...` was the **linux/amd64 platform
manifest**, not the multi-platform index, so `docker build --platform
linux/arm64` on the arm64 runner found no arm64 entry. The base is now
pinned to the OCI **index** digest (`sha256:e4db4c91...`, contains
linux/amd64 and linux/arm64/v8). Rule: a digest pin for a multi-arch image
must be the index digest; `docker buildx imagetools inspect` prints both,
and the platform manifests carry a `Platform:` line.
# Why `--ignore-scripts`
The `postinstall` script (`nuxt prepare`) runs before the source is copied
+5
View File
@@ -1,5 +1,10 @@
# Update Log
## 2026-10-31 (first release builds failed: pinned the amd64 manifest)
* **Fix**: [Dockerfile](../Dockerfile) and [Dockerfile.dev](../Dockerfile.dev) - the base digest `sha256:18f03e4b...` was the **linux/amd64 platform manifest**, so `docker build --platform linux/arm64` on the arm64 runner failed at `Build image` one second after the step started (run 157, v1.5.1; run 153, v1.5.0). Both now pin the multi-platform OCI **index** digest `sha256:e4db4c91...`, verified with `docker buildx imagetools inspect` to contain linux/amd64 and linux/arm64/v8. See [Production image shape](decisions/production-image.md).
* **Detail**: checkout, Docker CLI install, `Check daemon access`, registry login, the immutability guard and version resolution all passed - the runner and registry setup were correct; only the base image pin was wrong.
## 2026-10-31 (release-please component mismatch: no v1.5.0 tag)
* **Fix**: [release-please-config.json](../release-please-config.json) - removed `package-name: CV_Site_Frontend`. With `include-component-in-tag: false` the strategy component and the release PR body component are empty, but `getBranchComponent()` still returned `package-name`; the release phase logged `PR component: undefined does not match configured component: CV_Site_Frontend` and returned before creating the tag. The component now matches, so the next run should tag #35.