Go to file
James O. D. Hunt 09e316a376
Merge pull request #1848 from bergwolf/url
vc/readme: fix cri url
2019-07-02 08:37:51 +01:00
.ci ci: Build kata-runtime before running static checks 2019-05-21 11:56:14 -05:00
.github github: Add issue template 2018-03-22 13:56:43 +00:00
arch versions: update qemu version to 4.0.0 2019-06-05 10:20:00 -05:00
cli kata-check: add kvm extension check on aarch64 2019-06-20 10:23:13 +08:00
containerd-shim-v2 Merge pull request #1658 from xs3c/use-nonblock-for-stdin 2019-06-12 08:07:56 -07:00
data Merge pull request #1721 from devimc/topic/data/kataCollectSupportSnap 2019-05-24 15:38:42 +01:00
hack VMCache: the core and the client 2019-03-08 10:05:59 +08:00
netmon tests: Update test code to use test constraints 2019-05-02 15:42:35 +01:00
pkg trace: Add missing log message 2019-06-19 11:46:13 +01:00
protocols/cache factory: Make factory status can show status of VMCache server 2019-04-10 11:03:14 +08:00
vendor Unvendor: Unvendor firecracker-go-sdk 2019-06-18 16:38:53 -07:00
virtcontainers vc/readme: fix cri url 2019-07-01 20:14:13 -07:00
.gitignore configuration: add nemu support 2019-05-09 22:01:09 -07:00
.gitmodules submodules: Remove cc-runtime and runv 2018-03-21 12:10:15 -07:00
.travis.yml CI: Run .ci/setup.sh from tests repo 2019-07-01 16:24:51 -05:00
CODE_OF_CONDUCT.md docs: Add missing standard docs 2018-02-09 14:45:14 +00:00
CODEOWNERS ci: Add a CODEOWNERS file for github ack checks 2019-01-30 11:23:25 +00:00
CONTRIBUTING.md docs: Add missing standard docs 2018-02-09 14:45:14 +00:00
golang.mk Makefile: Change "GOPATH not set" to "No GO command or GOPATH not set" 2019-03-01 22:47:37 +08:00
Gopkg.lock Unvendor: Unvendor firecracker-go-sdk 2019-06-18 16:38:53 -07:00
Gopkg.toml Unvendor: Unvendor firecracker-go-sdk 2019-06-18 16:38:53 -07:00
LICENSE Initial commit 2017-11-21 17:03:45 +08:00
Makefile shimv2: Make shimv2 in case any source files change 2019-06-18 10:06:20 -07:00
README.md docs: Explain Kata Containers are Linux-based 2019-06-04 15:58:03 +01:00
VERSION release: Kata Containers 1.8.0-alpha2 2019-06-17 16:32:05 +08:00
versions.yaml Merge pull request #1813 from mcastelino/topic/fc_0_17_0 2019-06-21 16:03:03 -07:00

Build Status Build Status Go Report Card GoDoc

Runtime

This repository contains the runtime for the Kata Containers project.

For details of the other Kata Containers repositories, see the repository summary.

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 Linux containers running on Linux hosts.

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).

Download and install

Get it from the Snap Store

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

See the community repository.

Contact

See how to reach the community.

Further information

See the project table of contents and the documentation repository.

Additional packages

For details of the other packages contained in this repository, see the package documentation.