- s390x: fix gofmt complain - factory: Make VMCache and VM templating can work together - agent: pass correct mount type to agent for ephemeral volumes - network: Make tcfilter model as default - netmon: Fix bug in how routes are converted - shimv2 should return grpc error codes - Deprecate hyperstart, CC shim, and CC proxy - virtcontainers: inherit parent's CPU constraint - fix ut failure due to incorrect cleanup and make it runnable with non-root - storage: create k8s emptyDir inside VM - virtcontainers: prepend a kata specific string to host cgroups path - Factory: enable template feature for arm64 - cli: fix kata-check test - shimv2: fix the issue of stop container failed - split sandbox/container state - Make factory can control VMCache server - vc: remove spawner - s390x: fix golangci-lint complains - qemu: Remove the storage directories if qemu get from the factory - katautils: fix the issue of missing proxy debug config - vendor: update govmm - virtcontainers: Use only supported namespaces - cri-o: Update repository URLs - travis: use xenial - runtime: support memory hotplug via probe interface on aarch64 - s390x: not set socketID and threadID - config: fix panic in type assertion - Fix yq issuesa013f9b
s390x: fix gofmt complain3852682
network: Change the package level network default33bae70
network: Make tcfilter model as default343a0d3
factory: Make VMCache and VM templating can work togetherb08ab6a
vc: modify ioctl function to handle shim testc425079
vc: Deprecate CC proxy and shimc658770
vc: remove virtc api clid4ef9c0
vc: deprecate hyperstart agent8abd2ec
netmon: Fix bug in how routes are converted59e3956
virtcontainers: inherit parent's CPU constraintf512542
sandbox: return ErrNoSuchContainer when failing to find a container8215a3c
shimv2: convert vc errors to grpc errorscf90751
vc: export vc error types9040f6a
ut: fix UT failure due to incorrect cleanupa0f49a9
ut: fix UT failure due to non-root1a1f93b
virtcontainers: add a kata specific prefix to host cgroups pathf7223c6
shimv2: fix the issue of stop container failed76c4639
storage: create k8s emptyDir inside VM98687a3
Template: enable template for arm6416fe855
qemu: Remove the storage directories if qemu get from the factoryace8115
factory: Make factory status can show status of VMCache serverf639787
factory: Make factory destroy can stop VMCache server9ac6831
cli: fix kata-check testa63013d
vc: remove spawnerc414599
types: remove pid from sandbox state03ee25d
agent: treat container as shared pidns whenever it has pidns path616f26c
types: split sandbox and container state8041fc9
katautils: fix the issue of missing proxy debug configbb347ac
vendor: update govmm0b430dc
virtcontainers: Use only supported namespacese31b040
cri-o: Update repository URLea1df84
travis: use xenialb50292a
arm64: dep ensure to keep track of the revisons in kata agent3bfcdf7
agent: add interface memHotplugByProbe47670fc
memoryDevice: reconstruct memoryDevice30a6a7d
agent: acquire memory hotplug probe info via GetGuestDetails4993dff
ci: Add a failed execution check for curl7fa0390
ci: set $yq_version to 2.3.019458ec
s390x: fix golangci-lint49be8ee
s390x: not set socketID and threadID1b6affe
config: fix panic in type assertion2d422a8
agent: pass correct mount type to agent for ephemeral volumes228d151
mount: Add check for k8s host empty directory70c1931
mounts: Add check for system volumes 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
- 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
root
user, 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.