cairn

Reference

Copy the method

cairn is published to copy: the method and the code carry to another homelab, and the keys stay with whoever runs it.

Point a harness at it

start.txt briefs a coding agent: what cairn is, what to read and in which order, what to fork, and the first steps toward a base image and pipeline of its own. One line in a harness hands it over.

Read https://cairn.dunn.dev/start.txt and help me build my own homelab stack this way.

Fork it

What a fork supplies

A fork supplies seven things, and the first five need nothing sealed.

Those five are a registry path, the catalog's includes, a base flavor, a TPM with a recovery key, and a signing keypair. A sealed lane also needs a key set of the fork's own and a runner that can boot a virtual machine; rollback needs a health gate.

One lane

Fork cairn/example, keep the one lane that fits, and delete the other three.

plain has no disk encryption, attended unlocks by passphrase, edge unlocks itself from a TPM policy, and evidence adds signature checks to any of them. A fork builds on GitLab's shared runners as it stands.

Push

Edit the lane's Containerfile, push to main, and CI builds and promotes the image.

The instance component detects the change, builds, checks a bill of materials and tags :latest and :stable, on a base tag that already booted sealed in our CI.

Fig. Seven things a fork supplies, then the example's four lanes: one kept, pushed through detect, build and promote.

What a fork changes

  • Registry. instance_image follows the fork's project, so images land in its registry.
  • Image. The lane's Containerfile, and the base flavor it builds from.
  • Hosts. Users, SSH keys and services, in a private repository layered on the public image.
  • Keys. A fork that builds its own base mints its own set and never reuses ours.
  • Runners. base and the catalog default to our runner tags; a fork sets its own.

What a fork keeps

Our images boot under our keys. To try one as it stands, never install it with the firmware in Setup Mode, which can enrol our Secure Boot keys on the machine (base README).

Guide, chapter 34, Your lab

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 steps have their own page.