From 26d70bb1e62dbe221cdd76190f91b6ede8273b36 Mon Sep 17 00:00:00 2001 From: Christian Felder Date: Fri, 5 Mar 2021 18:16:05 +0100 Subject: [PATCH] index.md: fix small typo Signed-off-by: Christian Felder --- index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.md b/index.md index 2e8115c..0be3936 100755 --- a/index.md +++ b/index.md @@ -126,7 +126,7 @@ The architectural components are as follows: - CRI-O uses the `containers/image` library to pull the image from a container registry. - The downloaded image is unpacked into the container's root filesystems, stored in COW file systems, using containers/storage library. - After the rootfs has been created for the container, CRI-O generates an OCI runtime specification json file describing how to run the container using the OCI Generate tools. -- CRI-O then launches an OCI Compatible Runtime using the specification to run the container proceses. The default OCI Runtime is runc. +- CRI-O then launches an OCI Compatible Runtime using the specification to run the container processes. The default OCI Runtime is runc. - Each container is monitored by a separate `conmon` process. The conmon process holds the `pty` of the PID1 of the container process. It handles logging for the container and records the exit code for the container process. - Networking for the pod is setup through use of [CNI](https://github.com/containernetworking/cni), so any CNI plugin can be used with CRI-O.