Image support matrix
Kairos offers several pre-built images for user convenience based on popular Linux distributions such as openSUSE, Alpine Linux, and Ubuntu. The Kairos core team does its best to test these images, but those that are based on systemd (e.g. openSUSE, Ubuntu) are more thoroughly tested due to their homogenous settings. Support for other non-systemd based flavors (e.g. Alpine) may be limited due to team bandwidth. However, as Kairos is an open source community-driven project, we welcome any contributions, bug reports, and bug fixes. Check out our Contribution guidelines for more information.
In addition, tighter integration with systemd allows for several features that are only available with it, such as live layering.
These images are pushed to quay.io and are available for installation and upgrading. The installable mediums included in the releases are generated using the methods described in the automated installation reference, and the images can be used for upgrades as well.
Kairos release processes generates images based on official container images from popular Linux distributions. If you don’t see your preferred distribution, check if we are already planning support for it or create a new issue.
Below is a list of the available images and their locations on the quay.io registry:
- The Core images do not include any Kubernetes engine and can be used as a base for customizations.
- The Standard images include
k3sand the kairos provider, which enables Kubernetes deployments and optionally enables p2p.
- The -img repositories contain an img file which can be directly written to an SD card or USB drive for use with ARM devices.
Base images are tagged with specific upstream versions (e.g. Ubuntu 20 LTS is pinned to Ubuntu 20:04, openSUSE to openSUSE leap 15.4, etc.).
|Alpine Linux based (openSUSE kernel)||core, standard||core, core-img, standard, standard-img|
|Alpine Linux based (Ubuntu kernel)||core, standard|
|Debian based||core, standard|
|Fedora based||core, standard|
|openSUSE Leap based||core, standard||core, core-img, standard, standard-img|
|openSUSE Tumbleweed based||core, standard||core, standard|
|Ubuntu based (rolling) **||core, standard||core, core-img, standard, standard-img|
|Ubuntu based (22 LTS) **||core, standard||core, core-img, standard, standard-img|
|Ubuntu based (20 LTS) **||core, standard||core, core-img, standard, standard-img|
|Rocky Linux based||core, standard|
ubuntuflavor tracks the latest available Ubuntu release (at the time of writing 22.10). The LTS flavors, on the other hand, track the latest LTS available on DockerHub. For example, ubuntu-22-lts uses 22.04 as the base image.
The pipelines do not publish
img artifacts for the arm architecture because the files are too large for GitHub Actions (they exceed the artifact size limit). These artifacts can be extracted from the published docker images using the following command:
export IMAGE=quay.io/kairos/core-alpine-arm-rpi-img:v2.1.0 docker run -ti --rm -v $PWD:/image quay.io/luet/base util unpack "$IMAGE" /image
$IMAGE with the proper image)
The artifacts can be found in the
Kairos releases contains also the framework assets that can be used to build Kairos images from Scratch.
Framework images can be found in quay at: https://quay.io/repository/kairos/framework.
Each tag follow the convention:
Kairos follows Semantic Versioning and our releases signal changes to Kairos components, rather than changes to the underlying OS and package versions. Flavors are pinned to specific upstream OS branches (e.g.
leap 15.4) and major version bumps will be reflected through new flavors in our build matrix or through specific releases to follow upstream with regard to minor version bumps (e.g.
leap 15.3 and
Here are some key points to note:
- We only support the latest release branch with patch releases.
- Patch releases (e.g. 1.1.x) follow a weekly release cadence, unless there are exceptions for highly impactful bugs in Kairos itself or at the OS layer (e.g. high-severity CVEs).
- Minor releases follow a monthly cadence and are expected to bring enhancements through planned releases.
- Major releases signal new advanced features or significant changes to the codebase. In-place upgrades from old to new major release branches are not always guaranteed, but we strive for compatibility across versions.
In order to give users more control over the chosen base image (e.g.
Ubuntu, etc.) and reduce reliance on our CI infrastructure, we are actively working on streamlining the creation of Kairos-based distributions directly from upstream base images. You can track the development progress here.
If you need to further customize images, including changes to the base image, package updates, and CVE hotfixes, check out the customization docs.
Our changelog is published as part of the release process and contains all the changes, highlights, and release notes that are relevant to the release. We strongly recommend checking the changelog for each release before upgrading or building a customized version of Kairos.
Release changelogs are available for Kairos core and for each component. Below is a list of the components that are part of a Kairos release and their respective release pages with changelogs.
|Kairos provider (k3s support)||https://github.com/kairos-io/provider-kairos/releases|
Was this page helpful?
Awesome! Glad to hear it! Please tell us how we can improve.
Oh snap! Sorry to hear that. Please tell us how we can improve.