「Kata コンテナ」の版間の差分
Kusanaginoturugi (トーク | 投稿記録) (リンクを追加) |
Kusanaginoturugi (トーク | 投稿記録) (序文を訳出) |
||
7行目: | 7行目: | ||
{{Related|Podman}} |
{{Related|Podman}} |
||
{{Related articles end}} |
{{Related articles end}} |
||
+ | Kata Containers(以前の Clear Containers)は、OCI 互換のアプリケーションコンテナランタイムで、仮想化を利用して、潜在的に信頼できないプロセスを、ホストシステムや他のプロセスから隔離することを目的としています。現在、アップストリームでサポートされているハイパーバイザーは、{{pkg|qemu}}、{{aur|firecracker-bin}} と {{aur|cloud-hypervisor}} です。 |
||
− | Kata Containers (previously Clear Containers) is an OCI-compatible application container runtime meant to provide isolation of potentially untrusted processes from the host system and other processes by leveraging virtualization. Currently upstream-supported hypervisors are {{pkg|qemu}}, {{aur|firecracker-bin}} and {{aur|cloud-hypervisor}}. |
||
== Architecture == |
== Architecture == |
2021年5月19日 (水) 14:09時点における版
Kata Containers(以前の Clear Containers)は、OCI 互換のアプリケーションコンテナランタイムで、仮想化を利用して、潜在的に信頼できないプロセスを、ホストシステムや他のプロセスから隔離することを目的としています。現在、アップストリームでサポートされているハイパーバイザーは、qemu、firecracker-binAUR と cloud-hypervisorAUR です。
Architecture
kata-agent
- supervisor process running on the hypervised guest sandbox, tasked with managing its lifetimekata-runtime
- container runtime component responsible for handling commands specified by the OCI runtime specification and tasked with launching shimskata-proxy
(before 2.0) - routes I/O streams and signals between on-guest agent and host-side processes associated with running a given sandbox using gRPCkata-shim
(before 2.0) - container process monitor and reaperkata-ksm-throttler
(optional, before 2.0) -kata-linux-container
- patched kernel used to launch VMs serving as container/pod sandboxeskata-containers-image
- initramfs and rootfs images used for spawning VM sandboxes
Usage
Kata, by default, picks up its configuration from /etc/kata-containers/configuration.toml
, but that can be overridden by providing a path to configuration through the KATA_CONF_FILE
environment variable. Be sure to initialize configuration from /usr/share/defaults/kata-containers/configuration-qemu.toml
.
v1
Install the runtime kata-runtime-binAUR, kata-proxy-binAUR[リンク切れ: package not found], kata-shim-binAUR[リンク切れ: package not found], kernel kata-linux-container-binAUR and set of initrd and rootfs kata-containers-image-binAUR.
Docker
In order to use Kata Containers with Docker, the user needs to add it to supported runtimes in /etc/docker/daemon.json
:
{ "runtimes": { "kata": { "path": "/usr/bin/kata-runtime" } } }
To use it as the default runtime for Docker: {"default-runtime": "kata"}
.
To use it with the Firecracker hypervisor, due to its limitations, the devicemapper
storage driver [1] has to be used: {"storage-driver": "devicemapper"}
.
Afterward you can use the runtime key: docker run --runtime kata --rm -ti archlinux/base /bin/bash
.
Podman
Running a container: podman --runtime /usr/bin/kata-runtime run --rm -ti archlinux/base /bin/bash
.
Keep in mind that a Kata VM sandbox conceptually maps to Kubernetes pods or a shared netns, not just individual containers.
v2
Since release 2.0, Kata Containers exclusively uses OCI runtime shim API v2, however Docker has that API version hard-coded to v1, making it unfeasible to use this combination as of this writing.
Install the runtime kata2-runtime-binAUR, kernel kata2-linux-container-binAUR and set of initrd and rootfs kata2-containers-image-binAUR.
Containerd CLI
# ctr image pull docker.io/archlinux/base:latest # ctr run --rm -t --runtime io.containerd.kata.v2 docker.io/archlinux/base:latest example-container-name date