cairn

Reference

How we install

Every host installs the same way: a live environment under Secure Boot, one sealed image on an encrypted disk, a recovery passphrase, then an unlock posture.

The install takes one helper and one Ignition file, at https://cairn.dunn.dev/ignition.

1. Boot the live environment

Type the boot URL at the board's HTTP Boot setting:

https://cairn.dunn.dev/ipxe-shim.efi
http://cairn.dunn.dev/ipxe-shim.efi     # a board without HTTPS boot

It loads ipxe.efi beside it, an unmodified iPXE release signature-checked before it runs, so plain http suits these two alone. iPXE then boots Fedora CoreOS over https through Fedora's signed shim.

Fig. The live boot, on the board’s factory keys.

A USB stick is the fallback. media-check verifies both ISOs in CI and publishes each URL and sha256:

mkdir -p ~/cairn-media && cd ~/cairn-media
curl -fLO "$(cat fcos-live.url)" && shasum -a 256 -c fcos-live.sha256
diskutil unmountDisk /dev/diskN
sudo dd if=<iso> of=/dev/rdiskN bs=4m
sudo cmp -n "$(stat -f%z <iso>)" <iso> /dev/diskN

Boot off it, press e, and append ignition.config.url=https://cairn.dunn.dev/ignition. A second stick, Fedora Workstation, is for rescue.

2. Choose an image

Only sealed tags install; an unsealed tag leaves loader entries and nothing to load them (D27). A host installs its own repo's sealed tag; below, base:stable-sealed.

3. Install

REPO=registry.gitlab.com/dunn.dev/cairn/base/base
DIGEST=$(skopeo inspect --no-tags "docker://$REPO:stable-sealed" | jq -r .Digest)
cairn-install "$REPO@$DIGEST" "$REPO:stable-sealed" /dev/disk/by-id/...

cairn-install pulls the digest, re-checks it against the tag, has the disk path typed back, then runs bootc install to-disk with --composefs-backend --filesystem ext4 --block-setup tpm2-luks --generic-image. A sealed root needs the composefs backend, and tpm2-luks binds the encrypted root to the TPM. A fourth argument, direct, installs unencrypted.

The helper then sets secure-boot-enroll force in loader.conf, since systemd-boot's default enrols only in a VM. Only then do we enter Setup Mode: delete the Platform Key in firmware setup and reboot.

4. First boot

The installed system boots in Setup Mode, enrols our keys (D19) and unlocks from the installer's TPM slot, the only slot in the header. --generic-image writes no firmware boot entry, so the board boots the \EFI\BOOT\BOOTX64.EFI fallback or an entry added with efibootmgr.

Fig. Install to first boot, by the keys held.

5. Recovery passphrase, then a posture

A recovery passphrase comes first, the only way back if the TPM path breaks. Then the host takes one posture:

  • bind-tpm swaps the plain TPM binding for the signed policy of sealing (edge lane).
  • password-only retires the TPM slot and types the passphrase at every boot (attended lane).
  • tang unlocks root from a Tang server through the tang-initrd that ships in every flavor, and keeps the recovery passphrase (three added steps; keystone).
  • skip keeps the installer's binding.
Fig. What opens the disk under each posture.

docs/tpm-rebind.md has the exact commands for the first three, run by hand by choice (D14).

Copy the method