mirror of
https://github.com/aljazceru/kata-containers.git
synced 2026-01-30 03:34:29 +01:00
8befb1f39f
Update kata-deploy-binaries.sh cli options. Add options to allow ask build a tarball for a specific asset. It will help developers build a specific component and update a kata-deploy installation. Also build each asset independetly can help to create cache tarballs per asset in the future. e.g. Build a tarball with shimv2. ``` ./kata-deploy-binaries.sh --build=shim-v2 ``` Additionally, the script path is moved to a new directory as not only will work for releases. Signed-off-by: Carlos Venegas <jos.c.venegas.munoz@intel.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.