Repository navigation
feat: bt-layer --boot builds an appliance's boot layer - #20
Merged
Merged
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
marcos-mendez
force-pushed
the
feat/boot-layer
branch
from
October 8, 2026 07:03
abdc2e6 to
41b6ffa
Compare
Decision 0052: the kernel, initrd, firmware, bootloaders and installer leave the shared layers (common's plans/turnkey/base) for a boot layer per appliance, which only the ISO uses. bt-layer --boot APPLIANCE builds APPLIANCE-boot on top of the appliance's layer from products/boot ($BT_BOOT_PRODUCT to use another), whose plan is common's plans/keel-boot and whose conf and overlay are keel-boot. The container template is assembled from the appliance's chain without it.
marcos-mendez
force-pushed
the
feat/boot-layer
branch
from
October 8, 2026 07:13
41b6ffa to
67f8788
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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>(feat: the kernel, initrd, firmware, bootloaders and installer move to plans/keel-boot 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.