rackpi5
The image-only NixOS config that spore signs and serves, and that forge boots over HTTP when its NVMe does not boot.
| vendor | Raspberry Pi |
|---|---|
| model | Raspberry Pi 5, on forge's board |
| serial | n/a (image) |
| cpu | n/a (image) |
| ram | n/a (image) |
| storage | none (squashfs Nix store from spore, in RAM) |
| os | NixOS 26.05 (Yarara) |
rackpi5 is an image with no hardware of its own. nix/hosts/default.nix declares it with kind = "image". forge boots it when forge's NVMe does not boot.
What it runs#
rackpi5 is a stateless system in RAM with sshd. sshd accepts the SSH keys of jawn and of rowbutt, the host user for Rowbutt. spore signs and serves the image over HTTP. See Netboot.
Reach#
rackpi5 runs on forge's board, so it answers at forge.lolwtf.ca. Its host key differs from forge's and changes on each boot. Connect with a throwaway known_hosts:
ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no forge.lolwtf.caThe initrd sshd answers on port 2222 and accepts only jawn's keys.
Quirks#
- The image changes only when spore deploys a new generation.
Linked from 6
- forgeA Raspberry Pi 5 on NVMe that is the lab's native arm64 build host.
- HostsEvery host in the homelab, with its role, site, hardware, OS and status, and how to reach it.
- sporeA Raspberry Pi 5 on NVMe that serves x86 netboot, forge's HTTP boot image, the Talos boot image and Tinkerbell, lab DNS and time, and the SPIRE server.
- NetbootThe network boot service on spore, with TFTP and HTTP for folly's boot files and a signed RAM-boot image that forge falls back to.
- GlossaryThe lab-specific terms that the wiki pages use, what each means, and the page that defines it.
- Change the forge EEPROMChange the boot settings in the EEPROM of forge, and keep its HTTP boot fallback to the rackpi5 image.