kairos-init is an initializer for container images to be Kairosified.
You only need to run this once inside a Dockerfile to have a system that has all the necessary tools to run Kairos.
Create a Dockerfile with your desired base image, mount the kairos-init binary from the kairos-init image and run it:
FROM quay.io/kairos/kairos-init:latest AS kairos-init
FROM ubuntu:24.04
ARG VERSION=1.0.0
RUN --mount=type=bind,from=kairos-init,src=/kairos-init,dst=/kairos-init /kairos-init --version "${VERSION}"Then build it:
docker build -t my-kairosified-image .You can then use AuroraBoot to transform that image into an ISO, RAW image, or use it as an upgrade source for a running Kairos system.
Thor boards will not boot if the QSPI boot firmware version does not correspond to the L4T
version in the image. Kairos images pin L4T 39.2.
At install time, after-install-chroot runs /usr/sbin/kairos-jetson-qspi-update on boards
whose devicetree SoC compatible string is nvidia,tegra264 (uniform across every Thor
variant: AGX, IGX and devkit). It compares the board's firmware version (from the UEFI ESRT)
against the image's nvidia-l4t-bootloader version and:
- stages a UEFI capsule update when the image is newer — applied by UEFI on the next boot;
- does nothing when they match;
- aborts the install when the board firmware is newer than the image, because UEFI capsule update cannot downgrade firmware. Use a Kairos image matching the board, or reflash the board;
- aborts the install when the board is below L4T 38.0.0, which needs a USB host flash.
Override the L4T version with the L4T_VERSION environment variable.
For full documentation — including all available flags, configuration options, examples, extending stages, building for Trusted Boot, RHEL images, and more — please refer to the official Kairos documentation: