e7122b8862
Canonical, agent-agnostic procedure for bringing a new box into the flake, from a booted installer through to a deployable system, plus a thin Claude Code skill pointing at it -- same split as the nixpkgs upgrade procedure. Records the conventions that were not written down anywhere: sgdisk plus an LVM PV for the nix and persist volumes, adopting the installer's SSH host keys so secrets can be encrypted before first boot, and taking whatever show-hw-config emits that the flake's own modules do not already set. Also notes in AGENTS.md that a changed recipient list should be re-encrypted per file with ragenix --rekey-one; --rekey rewrites every secret in secrets/ and buries the actual change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2.4 KiB
2.4 KiB
installer
The custom NixOS installer image used to bootstrap new boxes.
- Source:
nixos/installer.nix - Host: — (a build target, not a deployed box)
Role
- Defines
nixos.systems.installer, a minimal server system rendered as a bootable ISO viaconfig.my.buildAs.iso(my.asISO); the same base can also be built as a kexec or netboot tree. - Build it with the devshell commands:
build-iso installer(orbuild-kexec installer/build-netboot installer). Theupdate-installercommand force-tagsinstallerto trigger a release rebuild in CI.
Image contents
- Broad hardware support (
my.build.allHardwarepulls in the nixpkgs all-hardware profile); EFI- and USB-bootable, zstd-compressed squashfs. Volume IDjackos-<release>-<arch>, menu label "/dev/player0 Installer", image base namejackos-installer. - Root SSH with the deploy key authorized (
PermitRootLogin prohibit-password); a randominstaller-<hex>hostname is set at boot. INSTALL_ROOT=/mntin the session environment, plus ashow-hw-configalias wrappingnixos-generate-config --show-hardware-config --root $INSTALL_ROOT.- NixOS documentation enabled, NetworkManager available but not started at boot (run
systemctl start NetworkManager, thennmtui), GC and memory-overcommit tuning for low-memory targets, LVM thin and NFS support. - Identifies itself as
VARIANT_ID=installerin/etc/os-release, and leaves the target's persistent pstore entries alone (Unlink=no) so an install doesn't evacuate them. - No regular user (
my.user.enable = false), no tmpfs-root management, no NAT, and not a deploy target (my.deploy.enable = false).
Installing a box
The end-to-end procedure — hardware inventory, partitioning, writing the box config, installing and
documenting it — is in install-box.md. The devshell's installer commands
(devshell/install.nix) drive an install over SSH against a booted
installer reachable at $INSTALLER:
installer-shell— get a shell on the installer.do-install <system>— builds the system's toplevel,nix copys the closure to the installer's$INSTALL_ROOTremote store, sets the system profile, touches/etc/NIXOS, and runsswitch-to-configuration bootwithNIXOS_INSTALL_BOOTLOADER=1(skip the bootloader with--no-bootloader, skip substitution with--no-substitute).