mirror of
https://github.com/aljazceru/kata-containers.git
synced 2025-12-30 20:44:26 +01:00
4f89e97e5e
When building the kata-deploy images before, we would look to pull the latest artifacts from the release URL. It would be better to allow the user to pull from this URL, or to create the artifacts locally, and pass the location of this tar.xz to the build process. Instead of providing KATA_VER, builders should provide KATA_ARTIFACTS, which is the filename that is assumed to be located within the docker build path. Signed-off-by: Eric Ernst <eric.ernst@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.