- Initrd fixes for ubuntu systemd - kernel: Add CONFIG_CGROUP_HUGETLB=y as part of the cgroup fragments - Fix kata-deploy to work on CI context - github-actions: Auto-backporting - runtime-rs: add support for core scheduling - ci: Use versions.yaml for the libseccomp - runk: Add cli message for init command - agent: add some logs for mount operation - Use iouring for qemu block devices - logging: Replace nix::Error::EINVAL with more descriptive msgs - kata-deploy: fix threading conflicts - kernel: Ignore CONFIG_SPECULATION_MITIGATIONS for older kernels - runtime-rs: support loading kernel modules in guest vm - TDX: Get TDX working again with Cloud Hypervisor + a minor change on QEMU's code - runk: Move delete logic to libcontainer - runtime: cri-o annotations have been moved to podman - Fix depbot reported rust crates dependency security issues - UT: test_load_kernel_module needs root - enable vmx for vm factory - runk: add pause/resume commands - kernel: upgrade guest kernel support to 5.19 - Drop-in cfg files support in runtime-rs - agent: do some rollback works if case of do_create_container failed - network: Fix error message for setting hardware address on TAP interface - Upgrade to Cloud Hypervisor v26.0 - runtime: tracing: End root span at end of trace - ci: Update libseccomp version - dep: update nix dependency - Updated the link target of CRI-O - libs/test-utils: share test code by create a new cratedc32c4622
osbuilder: fix ubuntu initrd /dev/ttyS0 hangcc5f91dac
osbuilder: add systemd symlinks for kata-agentc08a8631e
agent: add some logs for mount operation0a6f0174f
kernel: Ignore CONFIG_SPECULATION_MITIGATIONS for older kernels6cf16c4f7
agent-ctl: fix clippy error4b57c04c3
runtime-rs: support loading kernel modules in guest vmdc90eae17
qemu: Drop unnecessary `tdx_guest` kernel parameterd4b67613f
clh: Use HVC console with TDXc0cb3cd4d
clh: Avoid crashing when memory hotplug is not allowed9f0a57c0e
clh: Increase API and SandboxStop timeouts for TDXb535bac9c
runk: Add cli message for init commandc142fa254
clh: Lift the sharedFS restriction used with TDXbdf8a57bd
runk: Move delete logic to libcontainera06d819b2
runtime: cri-o annotations have been moved to podmanffd1c1ff4
agent-ctl/trace-forwarder: udpate thread_local dependency69080d76d
agent/runk: update regex dependencye0ec09039
runtime-rs: update async-std dependency763ceeb7b
logging: Replace nix::Error::EINVAL with more descriptive msgs4ee2b99e1
kata-deploy: fix threading conflicts731d39df4
kernel: Add CONFIG_CGROUP_HUGETLB=y as part of the cgroup fragments96d903734
github-actions: Auto-backportinga6fbaac1b
runk: add pause/resume commands8e201501e
kernel: fix for set_kmem_limit error00aadfe20
kernel: SEV guest kernel upgrade to 5.19.20d9d8d63e
kernel: upgrade guest kernel support to 5.19.257bd3f42d
runtime-rs: plug drop-in decoding into config-loading code87b97b699
runtime-rs: add filesystem-related part of drop-in handlingcf785a1a2
runtime-rs: add core toml::Value tree merging92f7d6bf8
ci: Use versions.yaml for the libseccompf508c2909
runtime: constify splitIrqChipMachineOptions2b0587db9
runtime: VMX is migratible in vm factory casefa09f0ec8
runtime: remove qemuPaths326f1cc77
agent: enrich some error code path4f53e010b
agent: skip test_load_kernel_module if non-root3a597c274
runtime: clh: Use the new 'payload' interface16baecc5b
runtime: clh: Re-generate the client code50ea07183
versions: Upgrade to Cloud Hypervisor v26.0f7d41e98c
kata-deploy: export CI in the build container4f90e3c87
kata-deploy: add dockerbuild/install_yq.sh to gitignore8ff5c10ac
network: Fix error message for setting hardware address on TAP interface338c28295
dep: update nix dependency78231a36e
ci: Update libseccomp version34746496b
libs/test-utils: share test code by create a new crate3829ab809
docs: Update CRI-O target linkfcc1e0c61
runtime: tracing: End root span at end of tracec1e3b8f40
govmm: Refactor qmp functions for adding block device598884f37
govmm: Refactor code to get rid of redundant code00860a7e4
qmp: Pass aio backend while adding block devicee1b49d758
config: Add block aio as a supported annotationed0f1d0b3
config: Add "block_device_aio" as a config option for qemub6cd2348f
govmm: Add io_uring as AIO type81cdaf077
govmm: Correct documentation for Linux aio.a355812e0
runtime-rs: fixed bug on core-sched error handling591dfa4fe
runtime-rs: add support for core scheduling09672eb2d
agent: do some rollback works if case of do_create_container failed Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>

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. |
libraries | core | Library crates shared by multiple Kata Container components or published to crates.io |
dragonball |
core | An optional built-in VMM brings out-of-the-box Kata Containers experience with optimizations on container workloads |
documentation | documentation | Documentation common to all components (such as design and install documentation). |
libraries | core | Library crates shared by multiple Kata Container components or published to crates.io |
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. |
runk |
utility | Standard OCI container runtime based on the agent. |
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.