7b63f210aa
- versions: Update Kubernetes, containerd and cri-o - virtcontainers: fix sandbox store struct VFIODevice bug - virtcontainers: Add function supportGuestMemoryHotplug - make: add ability to skip go version check - cli: Fix console for big endian architecture - virtcontainers: fix not close socket with ethtool - build: introduction of archConvertStatFs function - network: support hotplug a nic several times - sandbox: Extend sandbox API - golang.mk: Check and install yq before use it - cli: refactor the config into a separated package - newContainer: Not attach device if it is a CDROM - build: check golang version meets min req. - network: Use constant string for "none" network model - runtime,netmon: build as Position-Independent-Executable - virtcontainers: Rely on new interface LinkType field - enable default network endpoints hotplug for vm factory - cli: fix the issue of using wrong path to get version - cli: add guest hook path option (v2) - factory: use customised deep compare - qemu: query migrate status - Add support for ipvlan network driver - Add cgroup support - vfio: Change the way the driver is fetched - vendor: Rely on new agent package types - network: Use tc filtering rules in bridge mode - cli: add configuration option to use or not use host netns - versions: Update golang to 1.10.4 - network: Marshal BridgedMacvlanEndpoint and MacvtapEndpoint - device: fix the issue of passing wrong device address using virtio-blk - create/run: Make bundle path default to cwd - virtcontainers: Add missing API trace calls - sandbox/virtcontainers: memory resource hotplug when create container. - virtcontainers: Add missing API release calls - qemu: Disable the default romfile used by virtio-pci - Refactor network.go - network: Sort endpoints by name - virtcontainers: qemu: Add proper support for virt machine type - network: Add support for macvlan and macvtap driver - memory: update: Update state using the memory removed - block: Advertise block support for q35 - vendor: fix govmm package |
||
|---|---|---|
| .ci | ||
| .github | ||
| arch | ||
| cli | ||
| data | ||
| netmon | ||
| pkg | ||
| vendor | ||
| virtcontainers | ||
| .gitignore | ||
| .gitmodules | ||
| .pullapprove.yml | ||
| .travis.yml | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| golang.mk | ||
| Gopkg.lock | ||
| Gopkg.toml | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| VERSION | ||
| versions.yaml | ||
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.