mirror of
https://github.com/aljazceru/kata-containers.git
synced 2026-01-01 05:24:19 +01:00
cd6d364fba
Now crio.conf has some kata entries in by default, but commented out and without the runtime_path elements to them, our deploy script gets a little confused and fails to add the kata-qemu elements to the config. This is because the grep spots the commented out lines, and tries to, unsuccessfully, update the matching runtime_path elements, that don't actually exist. Improve this by matching only uncommented config lines, so now the script sees that the runtime is not really configured already, and instead of trying to edit/update it, will place a entry at the end of the file. Fixes: #928 Signed-off-by: Graham Whaley <graham.whaley@intel.com>
Kata Containers packaging
- Introduction
- Build using OBS
- 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 using OBS
See the OBS documentation.
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.
Credits
Kata Containers packaging uses packagecloud for package hosting.