kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Add hint about a potentially required configuration reset of containerd 

The added paragraph in the info-box would have saved me hours of troubleshooting. So I decided to suggest the addition, hoping to save other people some time.
pull/38397/head
ramobis 2022-12-11 12:02:30 +01:00 committed by GitHub
parent 694c4f7e92
commit 2d2ca3198b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/en/docs/setup/production-environment/container-runtimes.md
View File

@ -217,6 +217,8 @@ that the CRI integration plugin is disabled by default.
You need CRI support enabled to use containerd with Kubernetes. Make sure that `cri`
is not included in the`disabled_plugins` list within `/etc/containerd/config.toml`;
if you made changes to that file, also restart `containerd`.
If you experience container crash loops after the initial cluster installation or after installing a CNI, the containerd configuration provided with the package might contain incompatible configuration parameters. Consider resetting the containerd configuration with <code>containerd config default > /etc/containerd/config.toml</code> as specified in [getting-started.md](https://github.com/containerd/containerd/blob/main/docs/getting-started.md#advanced-topics) and then set the configuration parameters specified above accordingly.
{{< /note >}}
If you apply this change, make sure to restart containerd: