- Block: Add cache-related options for block devices - versions: Add nemu - Update cid vsock - shim: Add trace config option - vendor: Update govmm vendoring - git: Add containerd-shim-kata-v2 to .gitignore - virtcontainers: change uint32 to uint64 for ioctl - virtcontainers: Return the appropriate container status - config: Check factory config - Implement containerd shim v2 API for Kata Containers - ppc64le: kata-env fails due to missing vendor field - kata-check: do not require nested vt - kata-env: Show runtime trace settingdeb6f16virtcontainers: update context id of vsock to uint64f651147block: Add cache-related options for block devices018c8c1vendor: Update govmm vendoringea74b98shim: Add trace config option2af240bversions: Add nemu7093eecgit: Add containerd-shim-kata-v2 to .gitignore96ed6c5git: Sort .gitignore entries04ce4c0virtcontainers: change uint32 to uint64 for ioctl0bf29c8config: Check factory configfe784c1config: Create function to check config options70e4dc5config: Move check code to end of LoadConfigurationfa9b15dvirtcontainers: Return the appropriate container status02f8b29containerd-shim-kata-v2: add building of shimv2 into Makefile8199d10containerd-shim-kata: add unit test cases7951041containerd-shim-kata-v2: add the service Stats support5cc016ccontainerd-shim-kata-v2: add the service Kill support9ee53becontainerd-shim-kata-v2: add the service Resume support8df33d3containerd-shim-kata-v2: add the service Pause supportcd321a3containerd-shim-kata-v2: add the service ResizePty support47326f5containerd-shim-kata-v2: add the service Update support642231bcontainerd-shim-kata-v2: add the service Shutdown support87f591acontainerd-shim-kata-v2: add the service Connect supportec4f27bcontainerd-shim-kata-v2: add the service CloseIO support8c95b75containerd-shim-kata-v2: add the service Pids support709bc9acontainerd-shim-kata-v2: add the service Cleanup supporta0e6456containerd-shim-kata-v2: add the service Delete supportfd18b22containerd-shim-kata-v2: add the service State supportfbaefc9containerd-shim-kata-v2: add the service wait support269c940containerd-shim-kata-v2: add the exec service support4c5b296containerd-shim-kata-v2: add the start service support72fd6e0containerd-shim-kata-v2: add the create service supportca58bb4ppc64le: kata-env fails due to missing vendor fieldd6c4ca5container-shim-kata-v2: The init containerd shim v2 support5e6cd00containerd-shim-v2: add the shim v2 required vendorsf0cb0c7cli: refactor to align with katautils package9984636kata-env: Show runtime trace setting8cfb06fkata-check: optionally require kvm-intel unrestricted_guestacbcde3kata-check: do not require nested vtea9ecd7kata-check: modprobe missing kernel modules 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:
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.