Files
mesh-catalog/modules/distribution
jschoubben 6cf7f67a1d
mesh/delivery closed: a newer head of the same pull request
mesh/check checking 6cf7f67a1dfd on 08fbc51af26f
distribution's program listens on 5100 and the registry container on 5001, so no mapping names the store's port
The composer finds a listen's machine port in a container mapping that names
it on either side (MachineSide). The program's listen 5000 matched the
registry container's inner 5000 in 127.0.0.1:5001:5000, so the store's address
became the container's loopback side and the program's own port was never
opened: the move to 83cd1a3d on 2026-11-08 23:25 UTC cut the artifact store off
(issue 1966 note 109). The program now binds 5100, where every machine fetches
(the artifact-store alias and the seats' reach agree), and the container serves
5001 inside and out. A row holds that no container names 5100.

Undo: revert this commit.

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i
2026-11-09 01:40:49 +01:00
..

distribution

The distribution module of the mesh catalogue: runs the container image registry; holds the seats container-image-registry and oci-artifact-registry, and mesh-artifact-store until its window closes. It provides no provision: the store's address is its listen registry, open to the mesh, which every node-engine finds through the seat's holder (novox/hq ADR 0632). Its seats' list answers what the store holds, read from the store's own files through its container mesh-registry.

Files it does not know

Each directory or archive this module declares says how it treats a file it did not write (ADR 0422, ADR 0416).

  • /var/lib/mesh/registry: everything in it is the program's; the mesh moves nothing out (ADR 0422 §2).
  • /var/lib/mesh-registry: everything in it is the program's; the mesh moves nothing out (ADR 0422 §2).