distribution's program listens on 5100 and the registry container on 5001, so no mapping names the artifact store's port (issue 1966, recovery) #637

Merged
mesh-tools merged 2 commits from fix/1966-store-listen into main 2026-11-09 00:58:11 +00:00
2 Commits
Author SHA1 Message Date
jschoubben a0459a8553 distribution's manifest test reads the listens with its own struct and checks every mapping's sides for 5100
mesh/delivery merged: source.main moved to novox/mesh-catalog@ac94f8338f9c
mesh/check checking a0459a855311 on ac94f8338f9c
Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i
2026-11-09 01:42:40 +01:00
jschoubben 6cf7f67a1d distribution's program listens on 5100 and the registry container on 5001, so no mapping names the store's port
mesh/delivery closed: a newer head of the same pull request
mesh/check checking 6cf7f67a1dfd on 08fbc51af26f
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