jschoubben d47d231ec3 CAT-BI1: mesh-build-image publishes and copies through container-image-registry ...

A trunk image is written as an OCI layout and published by the seat's
publish and publish-part, only the parts the holder lacks; an upstream copy is
the seat's mirror, ended on the holder's published or refused. The module
holds no registry address: artifact-store, files/registry and the copier go,
and the step answers the seat's reference.

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

2026-11-04 15:48:55 +01:00

..

forge

Add mesh-build-image: rootless image builds with buildah, pushed by tag from trunk only (issue 1703)

2026-10-22 10:27:01 +02:00

gitconfig

Add mesh-build-image: rootless image builds with buildah, pushed by tag from trunk only (issue 1703)

2026-10-22 10:27:01 +02:00

known_hosts

Add mesh-build-image: rootless image builds with buildah, pushed by tag from trunk only (issue 1703)

2026-10-22 10:27:01 +02:00

settings.json

Build capacity is an integer per node layer, default 0: no manifest names a node's share (manifest side; the reader follows mesh-sdk S6)

2026-10-28 17:57:57 +01:00