Archived
jschoubben
604b04886b
It runs on a node, not in the control plane. Building needs a container runtime and a working tree, and the control plane deliberately cannot run commands on a machine — what it may send is bounded by the declaration language, and "run this build" is not in it. So the builder is something a node runs as a module, given work over the broker like anything else. The alternative, the control plane holding a docker socket, would make it the one component that can do anything anywhere, which is the property the whole design is arranged to avoid. A module repository has one file at its root, module.json, saying what it is and what it builds. A convention somebody can look for beats a setting somebody has to find. Properties that are decisions rather than details: - a fresh clone every time. A build reusing a working tree can succeed because of something a previous build left behind, and that is a build nobody can reproduce. - archives are packed deterministically — sorted, and carrying no timestamps, uid, gid or original names. Two builds of one commit must produce one digest, or nothing downstream can tell "this changed" from "this was built again", and every rebuild looks like a change to every machine holding it. - nothing is published until everything is built. Half a module in the store under a digest the mesh never records is reachable, unreferenced, and indistinguishable from something in use. The reproducibility test was passing for the wrong reason: both builds landed in the same second, so a packer carrying timestamps would still have agreed. It now stamps the two trees a year apart, and a timestamp in the header breaks it. One line is honest about not being independently tested: the sort before packing is belt and braces over filepath.Walk's documented lexical order, and no injection can distinguish it.