fix: the boot test reads the lnmp manifest from the assembled rootfs #6

Merged

navigator merged 1 commit from fix/boot-test-reads-manifest-from-rootfs into main

2026-10-17 23:30:45 -03:00

navigator commented

2026-10-17 23:17:37 -03:00

Owner

Fixes the boot test failure of the image gate (Keel-Linux/image-gate#10 and #11).

The runner container has no lnmp manifest. keel spec apply now reads the manifests from the assembled rootfs with --root. The layer ships the lnmp manifest.

Test: tests/boot-test.bats checks that the call passes --root "$BT_ROOTFS". Without the option, keel spec apply of the boot spec fails with the error of the issues.

Fixes the boot test failure of the image gate (Keel-Linux/image-gate#10 and #11). The runner container has no lnmp manifest. `keel spec apply` now reads the manifests from the assembled rootfs with `--root`. The layer ships the lnmp manifest. Test: tests/boot-test.bats checks that the call passes `--root "$BT_ROOTFS"`. Without the option, `keel spec apply` of the boot spec fails with the error of the issues.

navigator added 1 commit

2026-10-17 23:17:37 -03:00

fix: the boot test reads the lnmp manifest from the assembled rootfs

tests / package (pull_request) Successful in 6s

Details

tests / appliance (pull_request) Successful in 11s

Details

tests / tests (pull_request) Successful in 58s

Details

security / security (pull_request) Successful in 1m3s

Details

tests / stack (pull_request) Successful in 2m2s

Details

0e126ff714

The image gate boots the layer on a runner container that has no lnmp
manifest. The spec names the appliance, so "keel spec apply" stopped
with "lnmp is not an installed appliance under /usr/share/keel" and the
boot test failed before it started the container (image-gate#10 and
#11). The layer ships the manifest, so the boot test passes
--root "$BT_ROOTFS" and keel reads it from the rootfs, as "keel diff"
already does.