nats declares the upstream image it is built from #121

2026-09-27T21:40:33Z

jschoubben commented

2026-09-27 21:40:33 +00:00

The recipe started FROM the upstream server's digest directly, and the build machine refuses that: every base is declared under build.on and copied into the mesh's own store before a build, so a build never reaches out to a registry the mesh does not run (ADR 0097). Found the first time the module was built on a real mesh.

Same digest, now declared as NATS_BASE and arriving as a build argument. The Dockerfile says where it comes from and why the digest is the index's.

The recipe started `FROM` the upstream server's digest directly, and the build machine refuses that: every base is declared under `build.on` and copied into the mesh's own store before a build, so a build never reaches out to a registry the mesh does not run (ADR 0097). Found the first time the module was built on a real mesh. Same digest, now declared as `NATS_BASE` and arriving as a build argument. The Dockerfile says where it comes from and why the digest is the index's.

jschoubben added 1 commit 2026-09-27 21:40:34 +00:00

nats declares the upstream image it is built from 3f0a174392

The recipe started FROM the upstream server's digest directly, and the build machine
refuses that: every base is declared under build.on and copied into the mesh's own
store before a build, so a build never reaches out to a registry the mesh does not
run (novox/hq ADR 0097). Found the first time the module was built on a real mesh.

Same digest, now declared as NATS_BASE and arriving as a build argument; the
Dockerfile says where it comes from and why the digest is the index's.

jschoubben merged commit b1b18ae390 into main

2026-09-27 21:40:50 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#121