Issue 076 opened: a served fact made at first start cannot be served; ADR 0097's refusal of an undeclared base is live
This commit is contained in:
@@ -36,10 +36,11 @@ image the manifest did not declare is refused before the build, naming the image
|
||||
its own stages, declared arguments and `scratch` are not fetches. An unpinned vendor image is
|
||||
refused: a tag is what somebody else can move.
|
||||
|
||||
A recipe whose `FROM` names an undeclared base is **said, not yet refused**: the mesh's own images
|
||||
— the control plane's, the builder's, the tool runtime's — start from a public base and declare
|
||||
none, and refusing those refuses genesis. They declare their bases next; until then every build
|
||||
names the undeclared base and the remedy.
|
||||
A recipe whose `FROM` names an undeclared base was at first said, not refused: the mesh's own
|
||||
images — the control plane's, the tool runtime's, the route proxy's — started from a public base
|
||||
and declared none, and refusing those refuses genesis. *Amended the same day:* those three declare
|
||||
their bases now, and an undeclared `FROM` is refused like an undeclared copy. The builder's own
|
||||
image and the examples are built by `make`, not by the mesh, and take arguments with defaults.
|
||||
|
||||
The package half of the issue is not decided here: the mesh's package registry already proxies
|
||||
the public one, and the failure the report saw has to be run again to be placed.
|
||||
|
||||
Reference in New Issue
Block a user