fix(docker): pin the multi-platform base image index digest

The previous pin was the linux/amd64 platform manifest, so the arm64
runner failed instantly with 'no matching manifest for linux/arm64'.
Pin the OCI index digest that contains amd64 and arm64/v8.
This commit is contained in:
Noel Sabia committed 2026-10-31 21:08:39 +01:00
1 parent fdce59d77d
commit 7981575f86
4 files changed
+24 -5

No files matched your search

+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.