mirror of
https://github.com/aljazceru/kata-containers.git
synced 2026-01-27 10:14:27 +01:00
01481d6ac0
For Kata Containers 2.x, CRI-O should always be using the `containerd-shim-kata-v2` binary, and always be configured to use the "vm" runtime type, developed specifically for the shimv2, instead of the default "oci" runtime type. I've taken the liberty to try to simplify the CRI-O script and make it less error prone. In the future, we can start dropping a configuration file to /etc/crio/crio.conf.d and just removing it as part of the cleanup, but that's for the future. Fixes: #1357 Signed-off-by: Fabiano Fidêncio <fidencio@redhat.com>
Kata Containers packaging
- Introduction
- Build in a container
- Build a snap package
- Build static binaries
- Build Kata Containers Kernel
- Build QEMU
- Test Kata using ccloudvm
- Create a Kata Containers release
- Jenkins files
- Packaging scripts
- Credits
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 a snap package
Build static binaries
See the static build documentation.
Build Kata Containers Kernel
Build QEMU
Test Kata using ccloudvm
See the ccloudvm documentation.
Create a Kata Containers release
See the release documentation.
Jenkins files
See the Jenkins documentation.
Packaging scripts
See the scripts documentation.
Sync packages
See the kata-pkgsync documentation.
Credits
Kata Containers packaging uses packagecloud for package hosting.