Container build environments — kernel-builder, qemu-runner, ci-init, …
  • Dockerfile 87%
  • Nix 8.2%
  • Shell 4.8%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-07-19 06:38:36 +00:00
images fix(node-bootc): bump hc-utils pin 0.0.9 -> 0.0.8 (Hetzner pulled 0.0.9) 2026-07-19 08:37:20 +02:00
scripts feat(gate): AlmaLinux-everywhere linter + pin sysadmin nix base 2026-07-13 10:51:12 +02:00
README.md chore(builder-images): delete 9 orphaned images (zero consumers) 2026-07-12 10:20:57 +02:00

Builder Images

Container images used for building seanfarm infrastructure components.

Images

An image is onboarded (and built by the dockerfile-set pipeline) iff its dir carries a images/<name>/VERSION file. The list below is non-exhaustive — most images (pipeline-tools, envtest-tester, hetzner-builder, cast-render, ibmi-builder, zig-builder, zdns-builder, pipelines-ci, linux-kernel, zfs-userspace, node-bootc, …) are versioned per-image; see images/.

Image Purpose
kernel-builder Linux kernel + OpenZFS build environment (multi-arch cross-toolchains, sccache+ccache, mc, nfpm) on AlmaLinux 10
sysadmin One Image To Rule Them All — cluster admin CLIs + arbitrary OS image construction + OpenZFS userspace + grub2/xorriso + skopeo/buildah/oras/cosign + qemu + DNS/network diags (Nix flake; the one deliberate non-Alma exception)

Building

These images are built automatically by the ci-builder-images-pipeline Argo Workflow in the seanfarm cluster.

Trigger

Push commits to this repository to trigger a rebuild of all images.