jschoubben
e1a2fe7323
It carried the thing it was going to run; it now carries the thing that makes it. One artifact either way — but a mesh raised this way holds a control plane it built from a repository and a commit it can name, and can therefore build again. A mesh handed a finished image could not, and had no way to find that out until somebody needed it to. A build step sits between load and bundle, because the bundle must name an image and that image no longer arrives finished. Everything after it is unchanged: a locally built image is named by the digest of its own configuration, which is exactly what the carried one was named by. Refused in preflight when nothing says what to build, so a run that cannot finish says so before it has changed anything.
9 lines
397 B
Plaintext
9 lines
397 B
Plaintext
This is not a saved image. It is the placeholder that keeps this repository buildable.
|
|
|
|
A release build replaces this file with the output of `docker save` and puts it back afterwards:
|
|
|
|
make bootstrap IMAGE=mesh-control:<version>
|
|
|
|
An installer built with this file present carries no control plane, and says so in preflight
|
|
rather than getting a machine part-way to being a mesh and stopping.
|