- s390x: root parameter is missing - vc: qemu: fix error message on hotplug. - virtcontainers: set private propagation in rootfs - virtcontainers: ppc64le qemu does not have nvdimm capabilities yet - shimv2: use the UnmarshalAny() to unmarshal Protobuf.Any - runtime-v2: Make sure Shutdown() only shuts the server down - Add build support for the firecracker hypervisor - virtcontainers: Fix unit test typo - shimv2: multi wait support for wait service - update: allow do update on ready. - cli: fix parameter order error in cli/ps.go - virtcontainers: Add Asset, Capabilities and Bridge to the types package - katautils: Move SetKernelParams from CreateSandbox to updateRuntimeCo… - Versions: Add firecracker version - Hypervisor interface simplification - kata-runtime: Return correct kata-env on ppc64le - katautils: Remove unused argument containerID of function SetKernelPa… - kernel: Revert "versions: Bump to kernel 4.19.10" - versions: Bump to kernel 4.19.10 - Initial types package creation - cli: allow to kill a stopped container and sandbox - virtcontainers: Pass seccomp profile inside VM - First createSandboxFromConfig simplification - shimv2: get the kata configure file from env KATA_CONF_FILE - firecracker: Network API update - container: Use lazy unmount - block: Add new block storage driver "nvdimm"5329a71runtime-v2: Make sure Shutdown() only shuts the server downa07b4cdvirtcontainers: Fix unit test typof542233s390x: root parameter is missing18c7aa4virtcontainers: ppc64le qemu does not have nvdimm capabilities yet5ee838dshimv2: use the UnmarshalAny() to unmarshal Protobuf.Any7228babcontainer: update: Allow updates once container is created2e1ddbcvirtcontainers: Add Bridge to the types package5ba30fdshimv2: multi wait support for wait serviceb25f43evirtcontainers: Add Capabilities to the types package67e696bvirtcontainers: Add Asset to the types package6c3e0a9build: Add support for building firecracker hypervisor6fcb76cbuild: Handle qemu explicitly933b16fbuild: Improve quiet installa5a74f6vc: qemu: fix error message on hotplug.d4dd5f1qemu: fix gofmt import order.42a89d0katautils: Move SetKernelParams from CreateSandbox to updateRuntimeConfigabcc2d5Versions: Add firecracker versiondb33d71Kata-runtime: Use correct model name for TestGetCPUDetails11e24aakata-runtime: Return correct kata-env on ppc64le2c1b15dkernel: Revert "versions: Bump to kernel 4.19.10"b029e44virtcontainers: set private propagation in rootfsa02fd59virtcontainers: Remove code duplication in the test setupcf22f40virtcontainers: Remove the hypervisor waitSandbox method763bf18virtcontainers: Remove the hypervisor init methodfb149cekatautils: Remove unused argument containerID of function SetKernelParamsb05dbe3runtime: Convert to the new internal types package701afe9virtcontainers: First types package3ab7d07virtcontainers: Alias for pkg/typesc2c9c84virtcontainers: Conditionally pass seccomp profilebf2813fcli: allow to kill a stopped container and sandbox09168ccvirtcontainers: Call stopVM() from sandbox.Stop()acf833cvirtcontainers: Call agent startSandbox from startVMebf8547virtcontainers: Remove useless startSandbox wrapper0b28ab9shimv2: get the kata configure file from env KATA_CONF_FILE5c6d94dfirecracker: Revendor firecracker go sdk to 0.12.0ec5cf18firecracker: Network API updatedd28ff5memory: Add new option memory_offsetef75c3dblock: Add new block storage driver "nvdimm"c099be5container: Use lazy unmount802bfa2versions: Bump to kernel 4.19.1008f1c05Module: fix parameter order error in cli/ps.go Signed-off-by: katacontainers bot <katacontainersbot@katacontainers.io>
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.