Artifact Naming Convention
There are many different artifacts that Kairos produces. In this page we try to summarize them all and have a clear naming convention for them.
InfoArchitecture names are based on the Go architecture names, so
amd64is used instead of
OS images are stored in GitHub Releases, so the name of the artifact includes all the information about the image. The only exception is when the image is too big to be stored in GitHub Releases, in that case the image is stored in Quay.io.
The format of the name is the following:
<flavor>: Underlying Linux distribution e.g.
<device>: either the specific device name, e.g.
genericfor generic images
<version>: the version of Kairos e.g.
v1.0.0for Core, and can also include the K3S version e.g.
Kernel and RAM Disk Images
Kernel and RAM Disk images are stored in GitHub Releases and follow a similar convention to images, but they have no extension:
For iPXE we deliver three types of artifacts. The first one is the iPXE script, with the ipxe extension, and the other two are iPXE bootable images, with the iso and img extensions.
Reports are also stored in GitHub Releases and follow a similar convention to images, but they include the name of the report:
WarningThe repositories are not yet available, they will be published soon.
Container images are stored in Quay.io and follow the following convention:
This nomenclature for container images lacks some information for the following reasons:
- Docker repositories can be multi-arch, so the same image can be used in different architectures and therefore the name does not include the architecture.
- The version is not included in the image name, but in the tag.
- The name Kairos is already part of the repository name, so it is not included in the image name.
As mentioned before, some images are too big to be delivered via GitHub Releases, so they are stored in Quay.io. At the moment this is only for arm
The convention is the following:
All different framework flavors are stored in the same image, so the details are included in the tag. The name is simplified since not all attributes apply for framework images.
<name>: the name of the binary e.g.
<version>: the version of the binary e.g.
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.