mirror of
https://github.com/kata-containers/kata-containers.git
synced 2026-07-08 11:56:33 +00:00
df029f4f7a
The kata-deploy payload downloads the nydus-snapshotter host binaries (containerd-nydus-grpc, nydus-overlayfs) from the upstream per-arch release asset, which is glibc dynamically linked and fails to exec on musl-only hosts that have no glibc dynamic loader. nydus-snapshotter also publishes a statically linked release asset. Honour the existing STATIC_RUNTIME=yes umbrella flag (which already builds the kata Go host binaries static) in the nydus component build so that, with a single flag, the whole host-binary set of the payload is static and runs on a musl-only host. STATIC_RUNTIME=yes maps to a new STATIC_NYDUS_SNAPSHOTTER build-arg on the nydus downloader stage of Dockerfile.components, which selects the linux-static asset. The static nydus asset is published for amd64 only, so the build fails fast on other architectures when the flag is set. The default build is unchanged. Signed-off-by: Dimitris Karakasilis <dimitris@spectrocloud.com> Generated-By: Claude Opus 4.8 (1M context) noreply@anthropic.com
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
Build QEMU
Create a Kata Containers release
See the release documentation.
Packaging scripts
See the scripts documentation.
Credits
Kata Containers packaging uses packagecloud for package hosting.