github/containerd
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 2 Wiki Activity

Change the context to avoid misunderstandings

Browse Source 
Signed-off-by: Shuntaro Azuma <azush@amazon.com>
This commit is contained in:
Shuntaro Azuma 2022-02-09 20:56:11 +09:00 committed by a2ush
parent a9f61ba2c8
commit 7321032716
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/cri/architecture.md
View File

@ -9,7 +9,7 @@ The `cri` plugin uses containerd to manage the full container lifecycle and all
Let's use an example to demonstrate how the `cri` plugin works for the case when Kubelet creates a single-container pod:
* Kubelet calls the `cri` plugin, via the CRI runtime service API, to create a pod;
* `cri` creates and configures the pod’s network namespace using CNI;
* `cri` creates the pod’s network namespace, and then configures it using CNI;
* `cri` uses containerd internal to create and start a special [pause container](https://www.ianlewis.org/en/almighty-pause-container) (the sandbox container) and put that container inside the pod’s cgroups and namespace (steps omitted for brevity);
* Kubelet subsequently calls the `cri` plugin, via the CRI image service API, to pull the application container image;
* `cri` further uses containerd to pull the image if the image is not present on the node;