- qemu: use x-ignore-shared to implement vm template - virtiofs: Allow memory hotplug with virtiofs - Firecracker Add jailer support for firecracker - runtime: update govmm and move to virtio 1.0 for hotplugs - HV: kata-runtime support for ACRN hypervisor - versions: add crictl version which is compatible with OpenShift - versions: update CRI-O to v1.14.6 - Fix fork exec test errors - ci: Verify and block merge if other projects are not updated - shimv2: Add missing page size to Hugetlb Statd14968bqemu: use x-ignore-shared to implement vm templated392b22virtiofs: Allow memory hotplug with virtiofs050f8e9runtime: Disable disable-modern for virtio QMP add3e4989dvendor: update govmm and match code4fed346Firecracker: Enable jailer by default78ea50cvirtcontainers: Jailer: Add jailer support for firecracker98a6973virtcontainers: Add ACRN unit test casesf246a79virtcontainers: Add support for updating virtio-blk based container rootfsd9a4157virtcontainers: Add support for launching/managing ACRN based VMs828e0a2pkg/katautils: Add support for ACRN hypervisor configadcac93kata-check: Check and validate type-1 hypervisor for kata4d26ceeMake: Add ACRN hypervisor and generate configuration filebdd8947versions: add crictl version which is compatible with OpenShift098501aversions: update CRI-O to v1.14.64968438tests: Fix fork/exec test errorfcf9f9ftest: Fix fd leak causing test error5182a25ci: Verify and block merge if other projects are not updatedda7f5f3shimv2: Add missing page size to Hugetlb Stat Signed-off-by: Eric Ernst <eric.ernst@intel.com>
Runtime
This repository contains the runtime for the Kata Containers project.
For details of the other Kata Containers repositories, see the repository summary.
- Introduction
- License
- Platform support
- Download and install
- Quick start for developers
- Architecture overview
- Configuration
- Logging
- Debugging
- Limitations
- Community
- Further information
- Additional packages
Introduction
kata-runtime, referred to as "the runtime", is the Command-Line Interface
(CLI) part of the Kata Containers runtime component. It leverages the
virtcontainers
package to provide a high-performance standards-compliant runtime that creates
hardware-virtualized Linux containers running on Linux hosts.
The runtime is OCI-compatible, CRI-O-compatible, and Containerd-compatible, allowing it to work seamlessly with both Docker and Kubernetes respectively.
License
The code is licensed under an Apache 2.0 license.
See the license file for further details.
Platform support
Kata Containers currently works on systems supporting the following technologies:
- Intel VT-x technology.
- ARM Hyp mode (virtualization extension).
- IBM Power Systems.
- IBM Z mainframes.
Hardware requirements
The runtime has a built-in command to determine if your host system is capable of running a Kata Container:
$ kata-runtime kata-check
Note:
If you run the previous command as the
rootuser, further checks will be performed (e.g. it will check if another incompatible hypervisor is running).
Download and install
See the installation guides available for various operating systems.
Quick start for developers
See the developer guide.
Architecture overview
See the architecture overview for details on the Kata Containers design.
Configuration
The runtime uses a TOML format configuration file called configuration.toml.
The file contains comments explaining all options.
Note:
The initial values in the configuration file provide a good default configuration. You might need to modify this file if you have specialist needs.
Since the runtime supports a
stateless system,
it checks for this configuration file in multiple locations, two of which are
built in to the runtime. The default location is
/usr/share/defaults/kata-containers/configuration.toml for a standard
system. However, if /etc/kata-containers/configuration.toml exists, this
takes priority.
The command below lists the full paths to the configuration files that the runtime attempts to load. The first path that exists is used:
$ kata-runtime --kata-show-default-config-paths
Aside from the built-in locations, it is possible to specify the path to a
custom configuration file using the --kata-config option:
$ kata-runtime --kata-config=/some/where/configuration.toml ...
The runtime will log the full path to the configuration file it is using. See the logging section for further details.
To see details of your systems runtime environment (including the location of the configuration file being used), run:
$ kata-runtime kata-env
Logging
The runtime provides --log= and --log-format= options. However, the
runtime always logs to the system log (syslog or journald).
To view runtime log output:
$ sudo journalctl -t kata-runtime
For detailed information and analysis on obtaining logs for other system
components, see the documentation for the
kata-log-parser
tool.
Debugging
See the debugging section of the developer guide.
Limitations
See the limitations file for further details.
Community
Contact
See how to reach the community.
Further information
See the project table of contents and the documentation repository.
Additional packages
For details of the other packages contained in this repository, see the package documentation.