Skip to main content
Sidero Labs signs the container images generated for the Talos release with cosign:
  • ghcr.io/siderolabs/installer-base (base layer of the Talos installer)
  • ghcr.io/siderolabs/talos (Talos image for container runtime)
  • ghcr.io/siderolabs/talosctl (talosctl client packaged as a container image)
  • ghcr.io/siderolabs/imager (Talos install image generator)
  • all system extension images
Starting with Talos 1.14, the ghcr.io/siderolabs/installer image is no longer published: installer images are built and served by the Image Factory as factory.talos.dev/<platform>-installer/<schematic-id>:<version>, and are signed by the Image Factory service account rather than by the Talos release pipeline (see verifying image signatures).

Verifying container image signatures

The cosign tool can be used to verify the signatures of the Talos container images:
The image should be signed using cosign certificate authority flow by a Sidero Labs employee with an email from siderolabs.com domain or by a service account releasemgr-svc@talos-production.iam.gserviceaccount.com.

Reproducible builds

Talos builds for kernel, initramfs, talosctl, ISO image, and container images are reproducible. So you can verify that the build is the same as the one as provided on GitHub releases page. See building Talos images for more details.