mirror of
https://github.com/kata-containers/kata-containers.git
synced 2025-09-18 23:39:30 +00:00
9377c5d5ca
Althought, we changed the script "gen_versions_txt.sh" to accept a tag rather than a branch, this change is not sufficient. This script generates the right version file based on a tag, but function `get_from_kata_deps` does not use this, and ends up using the master branch instead. This is because this function looks at an env variable called $BRANCH and ends up using master branch if the variable is not defined. Pass the tag/new version to the build scripts, so that this tag is passed along to `get_from_kata_dep`. With this change, the correct version information is consumed by the build scripts for the various hypervisors and kernel. Fixes #831 Signed-off-by: Archana Shinde <archana.m.shinde@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.