6 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	d3ee49d6f3	F-host 2, ENG-5: on a fresh mesh the bootstrap pushes the holders' own images to the store on its loopback with no credential, and names them under the seat's reach (lead's design limit, review of issue 1966) ... The store's front is distribution's program, a bundle the mesh builds, so nothing serves it before the builder: the bootstrap's /v2/ wait and its pushes now go to the loopback port the store's manifest publishes, as the publish contract allows on the store's own node. The one-off credential and its file go: the runtime could not carry it on a push, and no push needs it. The tags list is asked for the repository being published, not always the control plane's. Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig	2026-11-04 16:29:56 +01:00
jschoubben	20614822df	F-host 2, ENG-5: the bootstrap's one-off push credential goes to distribution's account, mode 0600, only once the node-engine made that account and its state directory, so the holder's program can read it (review of issue 1966) ... The owner is the account the manifest names for the directory that holds the file; the bootstrap no longer makes that directory itself, and a run that reaches it first is refused naming what it waits on. Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig	2026-11-04 16:24:14 +01:00
jschoubben	18c1735f7c	ENG-5: the bootstrap makes a one-off push credential for the holders' first images, writes it for the store's holder and forgets it when its run ends (design 51, issue 1966) ... Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig	2026-11-04 12:07:34 +01:00
mesh-tools	52600ec7bd	Take the node-engine's parser from mesh-sdk: remaining imports (issue 1392)	2026-10-20 11:17:14 +00:00
jochen	0818e4c29a	Hold the trust-before-push order by a test, and refuse early what would stop it (issue 92) ... The fix is an order, and nothing failed if the trust call moved after the push or went: steps 7 and 8 are now one function a test drives against a runtime that refuses an untrusted push. Preflight now refuses, before anything is raised, a runtime file that is no JSON object, a docker.service that is not loaded and active, and a dockerd started with --insecure-registry, which would refuse the reload. The comment names the order the docker module's takeover rests on.	2026-10-12 16:29:14 +02:00
jochen	41e640d668	Have genesis trust its registry before pushing to it (issue 92) ... Genesis pushed the control plane's image to the mesh's plain-HTTP registry before anything told the container runtime to trust it; the docker module that writes that trust is applied long after. Genesis now writes the trust itself at the registry step, with the same into-json writer and a reload, for the address given and the node's mesh name on the node's registry port, and refuses before any push unless the runtime says it trusts each. The docker module later finds the mesh name there and takes it over without a change.	2026-10-12 16:13:11 +02:00