Go to file
Marco Vedovati c22b15d122 versions: Update golang to 1.11.10
Set the minimum golang version to 1.11.10, the latest stable 1.11 version
at the time of writing. Go 1.11 is required to build the agent with working
vsock support.

Fixes: #1693

Signed-off-by: Marco Vedovati <mvedovati@suse.com>
2019-05-16 19:03:19 +02:00
.ci Merge pull request #1414 from teawater/yq_version 2019-04-08 09:47:03 +01:00
.github
arch configuration: add nemu support 2019-05-09 22:01:09 -07:00
cli Merge pull request #1663 from egernst/nemu-config-adjustments 2019-05-14 10:51:01 -05:00
containerd-shim-v2 Merge pull request #1628 from lifupan/fixctx 2019-05-10 15:28:32 +08:00
data Merge pull request #1405 from jodh-intel/update-collect-script-for-dax-nvdimm-images 2019-03-22 09:54:03 +00: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 pkg/katautils: improve boot time disabling systemd units 2019-05-15 12:12:47 -05:00
protocols/cache factory: Make factory status can show status of VMCache server 2019-04-10 11:03:14 +08:00
vendor vendor: update govmm 2019-05-01 09:59:53 -04:00
virtcontainers Merge pull request #1668 from WeiZhang555/use-newstore 2019-05-16 17:38:30 +08:00
.gitignore configuration: add nemu support 2019-05-09 22:01:09 -07:00
.gitmodules
.travis.yml travis: use xenial 2019-04-08 13:58:17 -05:00
CODE_OF_CONDUCT.md
CODEOWNERS ci: Add a CODEOWNERS file for github ack checks 2019-01-30 11:23:25 +00:00
CONTRIBUTING.md
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 vendor: update govmm 2019-05-01 09:59:53 -04:00
Gopkg.toml vendor: update govmm 2019-05-01 09:59:53 -04:00
LICENSE
Makefile nemu-config: adjust defaults in configuration-nemu.toml 2019-05-13 15:35:04 -07:00
README.md doc: Fix broken internal link 2019-04-18 15:50:26 +01:00
VERSION release: Kata Containers 1.7.0 2019-05-15 17:44:36 -07:00
versions.yaml versions: Update golang to 1.11.10 2019-05-16 19:03:19 +02: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 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).

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.