How kairos-io/hadron works
Project type and purpose
• Hadron Linux is a minimal, foundational Linux distribution builder and image pipeline tailored for cloud and edge deployments.
• It assembles upstream-vanilla components (musl libc, systemd, Linux kernels), applies minimal patches, and outputs container images, ISOs, and VM-runnable artifacts.
• The Makefile, Dockerfile, and updatecli.d folder orchestrate build, update, and release processes; tests verify boot and upgrade functionality; docs describe architecture and usage.
File structure
• Top-level orchestrators:
• Makefile & Dockerfile – define build targets (build image, devel-iso, run-qemu, build-kairos, pull-image, etc.).
• updatecli.d – YAML recipes for automated dependency updates (kernel versions, tools, libraries).
• .github/workflows – CI pipelines for multi-arch builds, autobumping, example validation, docs deployment.
• Source inputs:
• files/ – configuration snippets, service unit files, shell profiles, patches to upstream components.
• patches/ – custom patch files applied to musl or other sources.
• examples/ – sample Dockerfiles illustrating how to extend or use Hadron.
• Documentation site:
• docs/ – Hugo site (config.toml, layouts, static assets) for online documentation, including architecture explanations.
• Tests:
• tests/ – Go test suite for acceptance tests (booting, secure-boot, FIPS, custom partitioning), assets for VM images and UEFI variables.
README for additional insights
• The architecture section describes core components (musl, systemd, kernel), boot methods (USI/UKI vs. GRUB), upgrade system (A/B atomic via Kairos agent).
• Development section reveals Make targets and build arguments (BOOTLOADER, KERNEL_TYPE, KUBERNETES_DISTRO/VERSION, ARCH, FIPS).
Final remarks
• Essential elements: inputs, orchestration logic, execution environment, outputs, testing, and CI/CD.
• Don’t over-engineer; separate the project into logical layers and components.