Go to file
Samuel Ortiz b05dbe3886 runtime: Convert to the new internal types package
We can now remove all the sandbox shared types and convert the rest of
the code to using the new internal types package.

This commit includes virtcontainers, cli and containerd-shim changes in
one atomic change in order to not break bisect'ibility.

Fixes: #1095

Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-01-08 14:43:33 +01:00
.ci make: notify user if yq is going to be installed 2018-11-16 18:56:46 +01:00
.github github: Add issue template 2018-03-22 13:56:43 +00:00
arch s390x: add support for s390x 2018-12-11 12:32:17 +01:00
cli runtime: Convert to the new internal types package 2019-01-08 14:43:33 +01:00
containerd-shim-v2 runtime: Convert to the new internal types package 2019-01-08 14:43:33 +01:00
data scripts: Use syntax highlighting in collect script 2018-09-24 09:22:54 +01:00
netmon virtcontainers: Alias for pkg/types 2019-01-08 14:24:06 +01:00
pkg virtcontainers: Conditionally pass seccomp profile 2019-01-08 10:22:23 +05:30
vendor firecracker: Revendor firecracker go sdk to 0.12.0 2018-12-27 19:47:17 -08:00
virtcontainers runtime: Convert to the new internal types package 2019-01-08 14:43:33 +01:00
.gitignore git: Add containerd-shim-kata-v2 to .gitignore 2018-12-03 08:57:46 +00:00
.gitmodules submodules: Remove cc-runtime and runv 2018-03-21 12:10:15 -07:00
.pullapprove.yml CI: Add doc team to pullapprove config 2018-03-22 15:49:27 +00:00
.travis.yml CI: travis: call yq installer 2018-10-30 15:44:40 +00:00
CODE_OF_CONDUCT.md docs: Add missing standard docs 2018-02-09 14:45:14 +00:00
CONTRIBUTING.md docs: Add missing standard docs 2018-02-09 14:45:14 +00:00
golang.mk make: notify user if yq is going to be installed 2018-11-16 18:56:46 +01:00
Gopkg.lock firecracker: Revendor firecracker go sdk to 0.12.0 2018-12-27 19:47:17 -08:00
Gopkg.toml firecracker: Revendor firecracker go sdk to 0.12.0 2018-12-27 19:47:17 -08:00
LICENSE Initial commit 2017-11-21 17:03:45 +08:00
Makefile virtcontainers: Conditionally pass seccomp profile 2019-01-08 10:22:23 +05:30
README.md docs: drop 's in architecture names for consistency 2018-12-17 16:18:16 +01:00
VERSION release: Kata Containers 1.5.0-rc2 2018-12-21 19:31:19 +00:00
versions.yaml Merge pull request #990 from alicefr/s390x 2018-12-11 10:57:27 -06: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):

$ 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

See the community repository.

Contact

See how to reach the community.

Further information

See the project table of contents and the documentation repository.