Ganesh Maharaj Mahalingam ceab0f0f1a ci: always use the versions from the local repository for CI
the versions.yaml file in runtime carries the information on all the
components we use and ship with kata. It would be nice to have the CI
test the newer versions when the file is changed and CI is triggered.
The current code always fetches from the master tree from github and
that does not help to validate version changes before it lands in the
tree.

Signed-off-by: Ganesh Maharaj Mahalingam <ganesh.mahalingam@intel.com>
2019-05-22 10:21:46 -07:00
2019-05-17 16:29:09 +01:00
2019-05-17 16:29:09 +01:00
2019-05-17 16:29:09 +01:00
2019-05-16 14:35:53 -05:00
2019-05-17 16:29:09 +01:00
2019-02-21 10:51:50 -06:00
2018-02-02 09:27:48 +00:00
2019-03-06 08:51:17 -06:00
2019-05-17 16:29:09 +01:00

Kata Containers packaging

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

See the snap documentation.

Build static binaries

See the static build documentation.

Build Kata Containers Kernel

See the kernel documentation.

Build QEMU

See the QEMU documentation.

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.

Description
No description provided
Readme Apache-2.0 71 MiB
Languages
Rust 57%
Go 27%
Shell 8%
RPC 5.9%
Makefile 1%
Other 1.1%