- Changes: - version: v1.14.6 - Add username and homedir to generated password - Close temporary image in PullImage - Version 1.14.6-dev - Version 1.14.5 - version: if git commit is empty, silently ignore - enable inline exec and attach test - Bump up minMemoryLimit to 12Mb - Backport CircleCI config - Fix up machine os content version and cri-o version in spec - Add state of infracontainer to disk when stopped - Use GlobalAuthFile when pulling the pause image if PauseImageAuthFile is not set - Don't discard copy.Options.SourceCtx when credentials are provided - Don't set non-default copy.Options in imageService.PullImage if it is nil - Add global_auth_file option to crio.image config - Create network and plugins directory if they do not exist - Disable file locking by default - Update containers/image to v2.0.0, buildah to 1.8.4, libpod to 1.4.1, ... - Bump github.com/containers/libpod from 1.2.0 to 1.3.1 - Vendor containers/storage v1.12.4 - update github.com/containers/* dependencies - Changes to rpm build and Dockerfile for ci - When plugin_dir is set, only use that value - Update Makefile to be usable without git - bump to version 1.14.5-dev - bump to version 1.14.4 - Default to runc is default_runtime is not set - Fix missing images names on list - Add crio-wipe - Add logic for running OpenShift CI on cri-o PRs - Update device cgroup permissions for configured devices. - version: v1.14.4-dev - version: v1.14.3 - Fix runtime panic when having concurrent writes to runtime impl map - server: do not add default /sys if bind mounted - Change plugin_dir to plugin_dirs - Added unit tests - Add version file functionality - fix build issues on 32-bit arches - conmon: use sd_journal_sendv - make vendor generated - Move to v1.14.3-dev - Tag v1.14.2 - Vendor in c/storage release-1.13 - Revert "update github.com/containers/* dependencies" - Update test suites - Fix logic of server.restore() - version: v1.14.2-dev Fixes #1866 Signed-off-by: Sascha Grunert <sgrunert@suse.com> |
||
---|---|---|
.ci | ||
.github | ||
arch | ||
cli | ||
containerd-shim-v2 | ||
data | ||
hack | ||
netmon | ||
pkg | ||
protocols/cache | ||
vendor | ||
virtcontainers | ||
.gitignore | ||
.gitmodules | ||
.travis.yml | ||
CODE_OF_CONDUCT.md | ||
CODEOWNERS | ||
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
- Download and install
- Quick start for developers
- Architecture overview
- Configuration
- Logging
- Debugging
- Limitations
- Community
- Further information
- Additional packages
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
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.
Additional packages
For details of the other packages contained in this repository, see the package documentation.