- stable-2.2 | Backport #2821 and #2769 - Backport runtime: Fix !x86 static checks - stable-2.2 | agent: exec should inherit container process capabilities - stable-2.2 | vendor: Update containerd to v1.5.7 - stable-2.2 | fc: fix version parsing for fc >= 0.25 - [backport] kata-monitor: cache improvementseea2c019virtcontainers: clh: Use 'quiet' as the default kernel parameter1e798b96virtcontainers: clh: Turn-off serial and virtio-console by default53c4492fagent: netlink: Use the grpc IP family field when updating the route893623dfruntime: Pass the route IP family to the agent503ce9c1agent: protos: Add a Family field to the Route payload9932e76fruntime: vendor: Bump the netlink package dependency0034f40bagent: exec should inherit container process capabilities1f6b0f65protection: add confidential compute frame for arm112e0f63check: fix typecheck failure in qemu_arm64_test.go18820e31virtcontainers: fix lint failure on ppc64le8fafced9virtcontainers: nolint guestProtection9668095aruntime: Fix field alignment on s390x3e145ea9vendor: Update containerd to v1.5.779e0754afc: fix version parsing for fc >= 0.25b8fc1af3runtime: set the sandbox storage path static97167ccdruntime: rename GetSanboxesStoragePath() --> GetSandboxesStoragePath()b0aca51ekata-monitor: bump version to 0.2.028873c4dkata-monitor: refresh kata sandbox list on fs events3525a2edkata-monitor: improve detection of kata workloads30d07d44kata-monitor: add getSandboxFS()623b1082runtime: add GetSandboxesStoragePath()fc1822f0kata-monitor: improve sandbox cachingba6ad1c8kata-monitor: warn when unable to retrive the lower level runtime22d3df91kata-monitor: minor fixes Signed-off-by: Fabiano Fidêncio <fidencio@redhat.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.
Getting started
See the installation documentation.
Documentation
See the official documentation (including installation guides, the developer guide, design documents and more).
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
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.