- volumes: Handle k8s empty-dirs of "default" medium type - versions: kernel: update to 4.19.28 - qemu: throw error when fail to get addr from bridges - vc:qemu: Fix id calculation of memory hotplug - s390x: 2 small test fixes - arm64: support NVDIMM - virtcontainers: move resource calculation to its own function - versions: update nemu to latest release - Add crio and containerd details to collect script - pkg: reduce memory footprint - Fix rootfs mount assumptions - s390x: fix golint complain - Network: remove Physical field in VethEndpoint - test: add tests for sandbox creation rollback and cleanup - VMCache: the new function that creates VMs as caches before using it - unit test: Fix local test - Add upstream version url regexp's to allow upto date checks - virtcontainer: watch the qemu's console when proxy's debug enabled - unit-test: fix undefined struct field SupportVSocks on arm64 - Makefile: Fix aarch64 fail in No GO command or GOPATH not set mode - tracing: Fix tracing - config: check the builtIn first when updating shim/proxy/agent - qemu: fix devID value error - Makefile: Change "GOPATH not set" to "No GO command"8e2a5eatests: Fix units tests to check empty-dir volumes backed by host-dir47a6023volumes: Handle k8s empty-dirs of "default" medium type4e81522vc:qemu: Fix id calculation of memory hotplug502fdabtest: add test for addDeviceToBridge0061e16virtcontainers: move resource calculation to its own function7504d9eunit-test: add TestSandboxUpdateResourcesf009a53versions: update nemu to latest releasef2a506ascripts: Add containerd details to collect script7266d31scripts: Log crio config file in collect script30f9776scripts: Create separate section for crio in collect scriptae08ea3scripts: Add helper function to collect scriptae4d8b4versions: kernel: update to 4.19.28c7ace4bqemu: throw error when fail to get addr from bridges2456ac5pkg: reduce memory footprintdf9a401Network: remove Physical field in VethEndpoint76d9db3vendor: Add github.com/gogo/protobuf45fe870runtime: Add unit tests0f8b2adVMCache: Update factory to run as a VMCache server90704c8VMCache: the core and the clientd8bcddbqemu-arm64: add unit test for func appendImage on aarch64986e4dcqemu-arm64: Support nvdimm on arm648ba27e1s390x: remove pmu from test6242af3s390x: fix TestQemuS390xMemoryTopology613edd5s390x: fix golint complain27a92f9runtime: Fix rootfs mount assumptionsc964a26virtcontainers: makefile fix .ci pathfcee080unit-test: Fix local testc4957ddvirtcontainer: watch the qemu's console when proxy's debug enabled1e30673test: add tests for sandbox creation rollback and cleanupbdb34e7Makefile: Fix aarch64 fail in No GO command or GOPATH not set modec759cf5tracing: Fix tracing31232b4config: check the builtIn first when updating shim/proxy/agent03dd780qemu: fix devID value errora1ddf53Makefile: Change "GOPATH not set" to "No GO command or GOPATH not set"35672b5unit-test: fix undefined struct field SupportVSocks on arm64975157dversions.yaml: add uscan annotations Signed-off-by: Peng Tao <bergwolf@gmail.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
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 containers.
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):$ sudo kata-runtime kata-check
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.