fix(deploy): bump gateway image digest to sha-9f1a081 [DEPLOY-IMG-FIX] #491

jason.woltje · 2026-04-22T02:25:55Z

jason.woltje commented

2026-04-22 02:25:55 +00:00

Summary

Bumps the federated-test stack gateway image to sha-9f1a081 (digest sha256:1069117740...), built from the corrected Dockerfile in #488. The previous M1 pin (sha256:9b72e2...) shipped with broken pnpm symlinks and could not boot.

Verification

Smoke-tested locally with the new digest:

$ docker run --rm <new-digest> sh -c 'ls /app/dist/main.js && du -sh /app/node_modules'
/app/dist/main.js
911.6M  /app/node_modules

$ docker run --rm -e DATABASE_URL=postgres://nope:nope@127.0.0.1:5/nodb ... <new-digest>
[Bootstrap] Tier detection failed: postgres unreachable at 127.0.0.1:5
TierDetectionError: ...
exit=0

This is the expected fail-fast path — imports resolve cleanly, bootstrap reaches the tier detector, and the gateway exits gracefully when the DB is unreachable. No MODULE_NOT_FOUND or import crash.

Required to unblock

DEPLOY-03 (mos-test-1.woltje.com stand-up)
DEPLOY-04 (mos-test-2.woltje.com stand-up)
DEPLOY-05 (TEST-INFRA.md authoring)

Notes

This is a one-line digest update inside deploy/portainer/federated-test.stack.yml.
The prior digest comment at the top of the file is updated to record the rationale.
A future PR will bump again once milestone tags supersede sha tags.

🤖 Generated with Claude Code

## Summary Bumps the federated-test stack gateway image to `sha-9f1a081` (digest `sha256:1069117740...`), built from the corrected Dockerfile in #488. The previous M1 pin (`sha256:9b72e2...`) shipped with broken pnpm symlinks and could not boot. ## Verification Smoke-tested locally with the new digest: ``` $ docker run --rm <new-digest> sh -c 'ls /app/dist/main.js && du -sh /app/node_modules' /app/dist/main.js 911.6M /app/node_modules ``` ``` $ docker run --rm -e DATABASE_URL=postgres://nope:nope@127.0.0.1:5/nodb ... <new-digest> [Bootstrap] Tier detection failed: postgres unreachable at 127.0.0.1:5 TierDetectionError: ... exit=0 ``` This is the expected fail-fast path — imports resolve cleanly, bootstrap reaches the tier detector, and the gateway exits gracefully when the DB is unreachable. No `MODULE_NOT_FOUND` or import crash. ## Required to unblock - DEPLOY-03 (mos-test-1.woltje.com stand-up) - DEPLOY-04 (mos-test-2.woltje.com stand-up) - DEPLOY-05 (TEST-INFRA.md authoring) ## Notes - This is a one-line digest update inside `deploy/portainer/federated-test.stack.yml`. - The prior digest comment at the top of the file is updated to record the rationale. - A future PR will bump again once milestone tags supersede sha tags. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

jason.woltje added 1 commit 2026-04-22 02:25:56 +00:00

fix(deploy): bump gateway image to sha-9f1a081 (Dockerfile fix from #488 )

ci/woodpecker/pr/ci Pipeline was successful

Details

ci/woodpecker/push/ci Pipeline was successful

Details

eede5756d9

The fed-v0.1.0-m1 image pin (sha256:9b72e2...) was built before the pnpm
deploy fix in #488 landed. That older image cannot resolve @mosaicstack/
storage at runtime and crashes during bootstrap.

The new digest sha256:1069117740e00ccfeba357cae38c43f3729fe5ae702740ce474f6512414d7c02
was published by Woodpecker pipeline 975 (commit 9f1a0818) using the
corrected Dockerfile and was smoke-tested locally:
  - imports resolve cleanly (no MODULE_NOT_FOUND)
  - bootstrap reaches tier-detector
  - tier detector fails fast with proper error when DB unreachable
  - exits 0 instead of crashing on import

Required to unblock DEPLOY-03/04 (mos-test-1 + mos-test-2 stand-up).

jason.woltje merged commit f2cda52e1a into main

2026-04-22 02:35:20 +00:00

jason.woltje referenced this issue from a commit

2026-04-22 02:35:23 +00:00

fix(deploy): bump gateway image digest to sha-9f1a081 [DEPLOY-IMG-FIX] (#491)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: mosaicstack/stack#491