Files
kata-containers/tools/packaging
Fabiano Fidêncio 443a999323 packaging: make payload/utility image registries substitutable for CI
Parameterize the remaining Docker Hub base images so CI can pull them from
the ghcr.io mirror without hardcoding it in the Dockerfiles:

  * kata-deploy/{Dockerfile,Dockerfile.components}, kata-monitor, kata-debug,
    kubectl, kata-webhook, dracut and the build-kata-deploy (dockerbuild)
    helper now use ARG IMAGE_REGISTRY=docker.io + FROM ${IMAGE_REGISTRY}/...
  * their build scripts pass --build-arg IMAGE_REGISTRY only when the env var
    is set (default behavior unchanged for local builds)
  * the build-kata-deploy-components CI jobs and publish-kata-images set
    IMAGE_REGISTRY=ghcr.io/kata-containers

The gcr.io/distroless runtime bases are intentionally left untouched.

Authored-by: Cursor <cursor@cursor.com>
Signed-off-by: Fabiano Fidêncio <ffidencio@nvidia.com>
2026-06-11 21:21:04 +02:00
..
2026-05-24 22:00:46 +02:00

Kata Containers packaging

Introduction

Kata Containers currently supports packages for many distributions. Tooling to aid in creating these packages are contained within this repository.

Build in a container

Kata build artifacts are available within a container image, created by a Dockerfile. Reference DaemonSets are provided in kata-deploy, which make installation of Kata Containers in a running Kubernetes Cluster very straightforward.

Build static binaries

See the static build documentation.

Build Kata Containers Kernel

See the kernel documentation.

Build QEMU

See the QEMU documentation.

Create a Kata Containers release

See the release documentation.

Packaging scripts

See the scripts documentation.

Credits

Kata Containers packaging uses packagecloud for package hosting.