- Fix cache factory UT - Virtio-fs v0.3 support - virtcontainers: set agent's logs vsock port - config: Fix `virtio-fs` typo in Makefile - Hypervisor: UUID fix for acrn hypevisor - virtcontainers: change firecracker socket permissions - Add annotations to provide custom configs - Fix CRIO + Firecracker - rootless: add rootless to kata - QEMU: do not require nvdimm machine option with initrd - s390x: Fix runtime build for s390x - versions: Update kernel to 4.19.75 - config: honor DEFSHAREDFS_QEMU_VIRTIOFS and CONFIG_QEMU_VIRTIOFS_IN - Support Firecracker 0.18 - virtcontainers: fix the issue of missing qemu error logs - config: Fix the qemu-virtiofs.toml - s390x: Share image between qemu instances - The unit of newMemory is MB - config: use 9p as default shared filesystem for nemu - Remove annotation config json keydd21046vc/store: fix TestStoreVCNewVCSandboxStore/TestStoreVCNewVCContainerStore6ab89e4vc/store: fix cache factory ut4863aa9vc/store: reuse storead15631virtiofsd: Do not use posix lock.2b40b6bvendor: update kata agentaa43e2avirtcontainers: set agent's logs vsock port23a5dc7virtiofsd: use virtiofsd --syslogd5a3d0avirtiofs: use virtiofsd --fd=FDNUM6ce6a26kata_agent: use virtio-fs 0.3+ mount options80855a8ci: travis: allow ppc64le failuresc3abd51config: Fix `virtio-fs` typo in Makefile8f6b0a6virtcontainers: change firecracker socket permissions8f70643tests: Remove hardcoded annotation value.e7b9c36tests: Add tests for annotations.09129c1config: Define minimum memory requirement8405b56annotations: add Annotations for the agent.5b78a8aannotations: Add annotations for runtime configafb91c2annotations: Add annotations to support additional configurations845bf73annotations: Support annotations to customise kata config30d0b7aannotations: Add missing firmware and hashes to asset annotations46b6815annotations: Change existing annotations to fit a new format312f3e7virtcontainers/fc: implement remove device7e9cc56virtcontainers/fc: improve create disk pool process07932d5virtcontainers/fc: add logs and improve others to make debugging easiered7240bvirtcontainers: move device operations to a more generic placee93bf96network: Add tuntap devicec8dd92ddep: update vendor packages for netlink commit41407cfvc: make cgroup usage configurable if rootless5f0799fvc: add rootless dir to path variablescdd6f7ekatautils: update paths to be configurable for rootless execution2d8b278rootless: add rootless logic8b843c5QEMU: do not require nvdimm machine option with initrdc152ebfs390x: Fix runtime build for s390xbc3c07bversions: Update kernel to 4.19.75aa6a16cHypervisor: UUID fix for acrn hypevisorb1909e8config: fix virtiofsd name84ead98config: add configuration-qemu-virtio-fs.toml to gitignore443e657config: honor DEFSHAREDFS_QEMU_VIRTIOFS and CONFIG_QEMU_VIRTIOFS_IN3d0949dvirtcontainers: check minimum supported version of firecracker1f93cffvirtcontainers: fix the issue of missing qemu error logs8680db6versions: update firecracker to the version 0.18.0123ba13vendor: update kata agent5ac6e9avirtcontainers: make socket generation hypervisor specificf2f0923virtcontainers: rename kataVSOCK type and move it into the types packagef42dd7dvirtcontainers/fc: Add support for hybrid vsocks2c4cf39virtcontainers/fc: bump firecracker experimental versionbb87b44virtcontainers/fc: Add logger to the http transport880bb2bvirtcontainers: introducing HybridVSock type2a8af23virtcontainers: Make fc.go fit the new API67ce728virtcontainers: Update firecracker swagger APIcdb1b5ccli: Fix the qemu-virtiofs.toml4134571config: do not use nemu variable for qemu-virtiofs configuration97fe749config: use 9p as default shared filesystem for nemuc81db9csandbox: The unit of newMemory is MB7fa0a72s390x: Share image between qemu instances7965baavendor: update govmm2ed94cbConfig: Remove ConfigJSONKey from annotations Signed-off-by: katacontainersbot <katacontainersbot@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
- 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 and creating a Kata Container:
$ kata-runtime kata-check
Note:
By default, only a brief success / failure message is printed. If more details are needed, the
--verboseflag can be used to display the list of all the checks performed.
rootpermission is needed to check if the system is capable of running Kata containers. In this case, additional checks are performed (e.g., 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.