feat: bt-layer --boot builds an appliance's boot layer #20
No reviewers
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Keel-Linux/buildtasks!20
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/boot-layer"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Decision 0052, point 1: every appliance gets a boot layer of its own, used only by the ISO.
Change
bt-layer --boot APP(also-b) builds the layerAPP-booton top ofAPP's layer fromproducts/boot. Set$BT_BOOT_PRODUCTto use a different product. It cannot be combined with--parent.products/boot: its plan is#include <keel-boot>(Keel-Linux/common#47), and its conf and overlay arekeel-booton top ofturnkey.d. As with every child layer, bt-layer applies onlyturnkey.d/hostname(plus the SSL ciphers when they are needed) andkeel-boot.tests/layer: covers the parsing, a--boot coreexport (delta, parent, conf, overlays, altstrap), a missing product,--boottogether with--parent, and the conf and overlaysproducts/bootresolves to against a stand-in turnkey.mk. kcov run locally: bt-layer 99.15 %, layer-lib 99.58 %.The container template is still assembled from
APP's chain without this layer. Keel-Linux/keel refuses a template that has any of these packages.keel-releaseis not changed here. Until the ISO builder exists, a release builds no boot layer (decision 0052, point 4). The ISO plan is in #21.Merge after Keel-Linux/common#47.
shellcheck /
LAYER_ERROR appears unused. Verify use (or export if used externally).
Show more details