- agent: change 9pfs mount option to cache=mmap - vc: qemu: Add config option to choose entropy source. - virtcontainers: revert "fix shared dir resource remaining" - block: Fix how rootfs is passed to kata-agent using virtio-blk - agent: clean up proxy process if start sandbox failed - config: Add Memory slots config - virtcontainers: support vhost and physical endpoints in AddInterface - device: Add GPU device support - virtcontainers: fix the issue of missing starting builtin proxy - Cleanup template properly - cli: add systemd-cgroup option - netmon: Add signals handler support - versions: update containerd version - scripts: Add throttler details to collect script - virtcontainers: hotplug memory with kata-runtime update command. - factory: start proxy before assign vm to a sandbox - virtcontainers: netmon: Monitor network changes - versions: Bump golang from 1.8.3 to 1.9.7 - cli: add configuration option to enable/disable vhost_net41619e4
vc: qemu: Add option to change entropy source9e606b3
virtcontainers: revert "fix shared dir resource remaining"58cf7fc
block: Fix how rootfs is passed to kata-agent using virtio-blkec87dca
virtcontainers: support vhost and physical endpoints in AddInterface19801bf
config: Add Memory slots configuration.bb513a7
agent: change 9pfs mount option to cache=mmap0ddf99d
agent: clean up proxy process if start sandbox failed5612694
virtcontainers: fix the issue of missing starting builtin proxy67ffa2f
factory: close factory in UTb193f0f
template: clean up template mountpoint on failures37b83c8
device: Add GPU device support2216d52
vendor: Update govmm to add vfio mediated device support on root bus048616f
netmon: Add signals handler1675410
pkg: signals: Factorize signals handling through a Go package723fbac
versions: update containerd version0075175
cli: add systemd-cgroup option6fc13e9
scripts: Add throttler details to collect script12a0354
sandbox: get and store guest details.13bf7d1
virtcontainers: hotplug memory with kata-runtime update command0928519
vendor: update agent to support memory update0ffe81c
cli: config: Make netmon configurable1406d99
virtcontainers: Start network monitor from virtcontainers29e2fa0
virtcontainers: Avoid conflict with network monitorf6ce465
vendor: Update agent vendoring55af108
netmon: Add unit testingf131590
netmon: Build netmon from the master Makefilefca7435
netmon: Add logrus supportbbf2a47
netmon: Don't rely on agent protocolb708a4a
netmon: Monitor network changesd75841e
ut: add more UTs07c1f18
factory: start proxy after create new VM4738d4e
agent: add setProxy/getAgentURL interface8f77c33
proxy: decouple from sandboxf39fa5d
proxy: remove newProxyConfigc41c9de
proxy: do not decode proxy config225e10c
cli: add configuration option to enable/disable vhost_net5ebb7cf
vendor: Update govmm to disable vhost when host doesn't support vhost-netd814bc5
versions: Bump golang from 1.8.3 to 1.9.7 Signed-off-by: Peng Tao <bergwolf@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
- 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
root
user, 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.