docs(live): record the Debian-Live appliance install and detached boot
Some checks are pending
ci / test (push) Waiting to run

The appliance ISO firmware-boots, installs (INSTALL_RC=0, NO_SECRET_LEAK) and
the installed disk boots detached as Gentoo-only (Portage, no apt, systemd
running, 0 failed units). Two anomalies are recorded rather than hidden: the
target hostname and a first-boot DHCP timing observation.
This commit is contained in:
Phoebus 2026-09-20 13:49:49 -07:00
parent d6fa7c8dce
commit 27795f7998
2 changed files with 47 additions and 4 deletions

View file

@ -4,10 +4,12 @@ Status: **In progress** · Author: session 2026-09-20 · Companion:
`docs/adr/0005-debian-live-appliance.md`
Progress: an actual ISO now builds with `installer/live/build.sh` (no root),
firmware-boots (UEFI), presents a serial console, and runs the static installer
from the live medium. A full install from the appliance reached the Portage
stage; the detached-boot verification is the remaining gate. See
`docs/VM-BOOT-VERIFICATION.md`.
firmware-boots (UEFI), presents a serial console, runs the static installer from
the live medium, completes a full install (`INSTALL_RC=0`, all stages,
`NO_SECRET_LEAK`), and the installed disk boots detached as a Gentoo-only
system (`running`, 0 failed units). Remaining: the `--check-live` preflight
(Phase 1), a reproducible in-repo ISO build check, and two open anomalies
(target hostname and DHCP timing) noted in `docs/VM-BOOT-VERIFICATION.md`.
This plan replaces the reference Gentoo LiveGUI medium as the *installer
appliance* with a Debian-Live image, while keeping the installed system 100%

View file

@ -282,6 +282,47 @@ binhost URI from the selected profile when it is not set. Signature
verification remains enabled. Publishing a matching systemd/desktop binhost is
the remaining step; no time estimate is claimed beyond the recorded ~26 min.
## Debian-Live installer appliance (actual ISO)
An appliance ISO was built **without root** by `installer/live/build.sh`
(Debian-Live 13.7 standard base + `/phoebus` overlay), SHA-256
`c0105bc9a282fddcbefab42baa577ea99843060f00fa45a75bcbc8358186bfd5`.
Firmware boot (UEFI/OVMF, no `-kernel`; the ISO's own grub chain):
- auto-boots the live system on the serial console;
- login `user` / `live` (passwordless sudo);
- the overlaid tools run: `cryptsetup 2.7.5`, `sgdisk 1.0.10`,
`partprobe 3.6`, `mkfs.btrfs 6.14`, `mkfs.fat`.
Full install to a fresh 24 GiB qcow2 driven from the appliance:
- `INSTALL_RC=0`, all stages, `NO_SECRET_LEAK`.
Detached boot of the installed disk (ISO removed):
- systemd-boot -> LUKS2 unlock -> `phoebus` login;
- `systemctl is-system-running` -> `running`; `0 loaded units listed`;
- **Gentoo-only**: `Gentoo Base System release 2.18`, Portage 3.0.82.2,
`no-apt`; systemd PID 1;
- `cryptroot` Btrfs mounted at `/`, `/home`, `/var`, `/.snapshots`, `/swap`,
ESP `/efi`.
This is Bash-free and Gentoo-target-only: the appliance contributes tooling,
never configuration.
### Open items found in this run
- The target came up with the default `gentoo` hostname (empty
`/etc/hostname`) even though the plan/config specified `phoebus`, unlike the
earlier Gentoo-appliance installs. Needs a focused look (possible stage3 or
ordering difference).
- The first detached boot reported `enp0s2 DOWN`; DHCP timing was not
re-checked. The earlier Gentoo-appliance boot had `enp0s2 UP 10.0.2.15/24`.
Neither affects the proven Gentoo-appliance boot path; both are recorded rather
than hidden.
## Known remaining work
- The graphical session was verified with the **headless** wlroots backend