Files
kata-containers/tools/packaging
Manuel Huber 03f8e9c70e ci: cover EROFS snapshotter default_size=0 path
kata-deploy currently hard-codes the EROFS snapshotter
default_size to "10G", so the CoCo EROFS CI lane only
exercises the path where the snapshotter provides an rwlayer.

Add a kata-deploy and Helm knob for the EROFS default_size
and thread it through the Kubernetes CI helpers. Keep the
default at "10G" to preserve current behavior, but allow the
workflow to set "0" for the runtime-rs no-rwlayer path.

Expand the existing EROFS snapshotter job to run both values.
The setting is written to containerd as a TOML string so "0"
is not parsed as an integer.

Signed-off-by: Manuel Huber <manuelh@nvidia.com>
2026-05-11 17:52:32 +00:00
..
2026-01-12 15:48:44 +01:00
2026-02-18 18:18:52 +01:00
2023-06-12 09:24:09 +01:00
2023-06-12 09:24:09 +01:00
2023-06-12 09:24:09 +01: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.