- agent: fix container stop error with signal SIGRTMIN+3 - doc: Improve kata-deploy README.md by changing sh blocks to bash blocks - docs: Remove kata-proxy reference - kata-monitor: fix duplicated output when printing usage - Stop getting OOM events from agent for "ttrpc closed" error - tools/packaging: Fix error path in `kata-deploy-binaries.sh -s` - kata-deploy: fix version bump from -rc to stable - release: Include all the rust vendored code into the vendored tarball - docs: Remove VPP documentation - runtime: Remove the explicit VirtioMem set and fix the comment - tools/packaging/kata-deploy: Copy install_yq.sh before starting parallel builds - docs: Remove kata-proxy references in documentation - agent: Signal the whole process group - osbuilder/qat: don't pull kata sources if exist - docs: fix markdown issues in how-to-run-docker-with-kata.md - osbuilder/qat: use centos as base OS - docs: Update vcpu handling document - Agent: fix unneeded late initialization lint - static-build,clh: Add the ability to build from a PR - Don't use a globally installed mock hook for hook tests - ci: Weekly check whether the docs url is alive - Multistrap Ubuntu & enable cross-building guest - device: using const strings for block-driver option instead of hard coding - doc: update Intel SGX use cases document - tools: update QEMU to 6.2 - action: Update link for format patch documentation - runtime: properly handle ESRCH error when signaling container - docs: Update k8s documentation - rustjail: optimization, merged several writelns into one - doc: fix kata-deploy README typo - versions: Upgrade to Cloud Hypervisor v22.1 - Add debug and self-test control options to Kata Manager - scripts: Change here document delimiters - agent: add tests for get_memory_info function - CI: Update GHA secret name - tools: release: Do not consider release candidates as stable releases - kernel: fix cve-2022-0847 - docs: Update contact link in runtime README - Improve error checking of hugepage allocation - CI: Create GHA to add PR sizing label - release: Revert kata-deploy changes after 2.4.0-rc0 release |
||
---|---|---|
.github/workflows | ||
ci | ||
docs | ||
snap | ||
src | ||
tools | ||
utils | ||
.gitignore | ||
CODE_OF_CONDUCT.md | ||
CODEOWNERS | ||
CONTRIBUTING.md | ||
Glossary.md | ||
LICENSE | ||
Makefile | ||
README.md | ||
utils.mk | ||
VERSION | ||
versions.yaml |

Kata Containers
Welcome to Kata Containers!
This repository is the home of the Kata Containers code for the 2.0 and newer releases.
If you want to learn about Kata Containers, visit the main Kata Containers website.
Introduction
Kata Containers is an open source project and community working to build a standard implementation of lightweight Virtual Machines (VMs) that feel and perform like containers, but provide the workload isolation and security advantages of VMs.
License
The code is licensed under the Apache 2.0 license. See the license file for further details.
Platform support
Kata Containers currently runs on 64-bit systems supporting the following technologies:
Architecture | Virtualization technology |
---|---|
x86_64 , amd64 |
Intel VT-x, AMD SVM |
aarch64 ("arm64 ") |
ARM Hyp |
ppc64le |
IBM Power |
s390x |
IBM Z & LinuxONE SIE |
Hardware requirements
The Kata Containers runtime provides a command to determine if your host system is capable of running and creating a Kata Container:
$ kata-runtime check
Notes:
This command runs a number of checks including connecting to the network to determine if a newer release of Kata Containers is available on GitHub. If you do not wish this to check to run, add the
--no-network-checks
option.By default, only a brief success / failure message is printed. If more details are needed, the
--verbose
flag can be used to display the list of all the checks performed.If the command is run as the
root
user additional checks are run (including checking if another incompatible hypervisor is running). When running asroot
, network checks are automatically disabled.
Getting started
See the installation documentation.
Documentation
See the official documentation including:
Configuration
Kata Containers uses a single configuration file which contains a number of sections for various parts of the Kata Containers system including the runtime, the agent and the hypervisor.
Hypervisors
See the hypervisors document and the Hypervisor specific configuration details.
Community
To learn more about the project, its community and governance, see the community repository. This is the first place to go if you wish to contribute to the project.
Getting help
See the community section for ways to contact us.
Raising issues
Please raise an issue in this repository.
Note: If you are reporting a security issue, please follow the vulnerability reporting process
Developers
See the developer guide.
Components
Main components
The table below lists the core parts of the project:
Component | Type | Description |
---|---|---|
runtime | core | Main component run by a container manager and providing a containerd shimv2 runtime implementation. |
agent | core | Management process running inside the virtual machine / POD that sets up the container environment. |
documentation | documentation | Documentation common to all components (such as design and install documentation). |
tests | tests | Excludes unit tests which live with the main code. |
Additional components
The table below lists the remaining parts of the project:
Component | Type | Description |
---|---|---|
packaging | infrastructure | Scripts and metadata for producing packaged binaries (components, hypervisors, kernel and rootfs). |
kernel | kernel | Linux kernel used by the hypervisor to boot the guest image. Patches are stored here. |
osbuilder | infrastructure | Tool to create "mini O/S" rootfs and initrd images and kernel for the hypervisor. |
agent-ctl |
utility | Tool that provides low-level access for testing the agent. |
trace-forwarder |
utility | Agent tracing helper. |
ci |
CI | Continuous Integration configuration files and scripts. |
katacontainers.io |
Source for the katacontainers.io site. |
Packaging and releases
Kata Containers is now available natively for most distributions. However, packaging scripts and metadata are still used to generate snap and GitHub releases. See the components section for further details.
Glossary of Terms
See the glossary of terms related to Kata Containers.