- sandbox: cleanup sandbox if creation failed - mounts: Ignore existing mounts if they cannot be honored - config: Add firecracker as a supported hypervisor configuration - Firecracker: virtio mmio support - Firecracker VMM support - shimv2: discard log before shim init log output - virtcontainers: cgroups: Don't error if no thread ID - Copy files from host to guest - katautils: check config factory/template and vsock - virtcontainers: Add context when creating tests sandboxes - make: Add "GOPATH not set" - virtcontainers: network: Use multiqueue flag only when appropriate - katautils: fix the issue of shimv2 boot failed with vsock enabled - docs: add IBM Z in the README - qemu-arm64: refactor 'console=hvc0,hvc1' for kata-agent debugging - network: Don't assume multiple queues support by default - virtcontainers: make sandbox manage VM resources - factory: set guest time after resuming - shimv2: fix the error of reaping qemu process mistakenly - s390x: add support for s390x - config: Add cache-related options for block devices83e38c9mounts: Ignore existing mounts if they cannot be honoredbf1a5cesandbox: cleanup sandbox if creation failed0d84d79virtio-mmio: Add support for virtio-mmio353564aconfig: Reorganize the code to fix code complexityd6c1f53config: Add firecracker configuration supportb4c3a2fvirtcontainers: fc: Stop the VM by killing the processfba2379firecracker: Add support for pseudo hotplug22ebc09firecracker: Close the vsock vhostfde65bafavirtcontainers: Add firecracker as a supported hypervisorc1d3f1afirecracker: VMM API supportc34b045firecracker: vendor in all firecracker dependenciesa21d1e6virtcontainers: cgroups: Don't error if no thread ID378d815virtcontainers: copy or bind mount shared filebc31844virtcontainers: Check file sharing support6291762virtcontainers: copy files form host to guestdcd48a9vc: capabilities: add capability flags for filesystem sharinge776380vendor: update kata agente4e7c3akatautils: check config template and vsock0f1fde4virtcontainers: network: Use multiqueue flag only when appropriatef63a18dvirtcontainers: Add context when creating tests sandboxes05be5bfshimv2: discard log before shim init log outpute98dee6docs: drop 's in architecture names for consistency1892102docs: add IBM Z in the README573b73ekatautils: fix the issue of shimv2 boot failed with vsock enabledc8c564bqemu-arm64: refactor 'console=hvc0,hvc1' for kata-agent debugginga1af1cbvirtcontainers: network: Rely on hypervisor capabilities for multi queuesa227ab8virtcontainers: hypervisor: Add capability regarding multiqueue support0bcd221virtcontainers: network: Rename numCPUs to queues2cb4bb9virtcontainers: network: Reorganize endpoints interconnectiond4586d4test: remove TestHotplugRemoveMemory0d80202vc:sandbox: rename newcontainer to fetchcontainer.618cfbfvc: sandbox: Let sandbox manage VM resources.2535844make: Add "GOPATH not set"8444a7afactory: set guest time after resumingf813708vendor: update agent vendor for SetGuestDateTime6f83061s390x: add support for s390xdf8b7dbshimv2: fix the issue of reaping child mistakenlye4a3fd5vendors: upgrade the containerd vendors6024088config: Add cache-related options for block devices 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
- Quick start for users
- 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
Quick start for users
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.