whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #33314 from my-git9/debug-cluster-crictl

Browse Source 
[en] modify  link debug-cluster/crictl
This commit is contained in:
Kubernetes Prow Robot
2022-04-30 05:35:13 -07:00
committed by GitHub
parent ced5dc9fa7 5810ecfd49
commit 20ce068d30
4 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/blog/_posts/2020-12-02-dockershim-faq.md
+1 -1
View File
@@ -155,7 +155,7 @@ runtime where possible.
Another thing to look out for is anything expecting to run for system maintenance Another thing to look out for is anything expecting to run for system maintenance
or nested inside a container when building images will no longer work. For the or nested inside a container when building images will no longer work. For the
former, you can use the [`crictl`][cr] tool as a drop-in replacement (see [mapping from docker cli to crictl](https://kubernetes.io/docs/tasks/debug-application-cluster/crictl/#mapping-from-docker-cli-to-crictl)) and for the former, you can use the [`crictl`][cr] tool as a drop-in replacement (see [mapping from docker cli to crictl](https://kubernetes.io/docs/tasks/debug/debug-cluster/crictl/#mapping-from-docker-cli-to-crictl)) and for the
latter you can use newer container build options like [img], [buildah], latter you can use newer container build options like [img], [buildah],
[kaniko], or [buildkit-cli-for-kubectl] that don’t require Docker. [kaniko], or [buildkit-cli-for-kubectl] that don’t require Docker.
content/en/blog/_posts/2022-02-17-updated-dockershim-faq.md
+1 -1
View File
@@ -169,7 +169,7 @@ runtime where possible.
Another thing to look out for is anything expecting to run for system maintenance Another thing to look out for is anything expecting to run for system maintenance
or nested inside a container when building images will no longer work. For the or nested inside a container when building images will no longer work. For the
former, you can use the [`crictl`][cr] tool as a drop-in replacement (see [mapping from docker cli to crictl](https://kubernetes.io/docs/tasks/debug-application-cluster/crictl/#mapping-from-docker-cli-to-crictl)) and for the former, you can use the [`crictl`][cr] tool as a drop-in replacement (see [mapping from docker cli to crictl](https://kubernetes.io/docs/tasks/debug/debug-cluster/crictl/#mapping-from-docker-cli-to-crictl)) and for the
latter you can use newer container build options like [img], [buildah], latter you can use newer container build options like [img], [buildah],
[kaniko], or [buildkit-cli-for-kubectl] that don’t require Docker. [kaniko], or [buildkit-cli-for-kubectl] that don’t require Docker.
content/en/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm.md
+1 -1
View File
@@ -93,7 +93,7 @@ This may be caused by a number of problems. The most common are:
configure it properly see [Configuring a cgroup driver](/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver/). configure it properly see [Configuring a cgroup driver](/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver/).
- control plane containers are crashlooping or hanging. You can check this by running `docker ps` - control plane containers are crashlooping or hanging. You can check this by running `docker ps`
and investigating each container by running `docker logs`. For other container runtime see and investigating each container by running `docker logs`. For other container runtime see
[Debugging Kubernetes nodes with crictl](/docs/tasks/debug-application-cluster/crictl/). [Debugging Kubernetes nodes with crictl](/docs/tasks/debug/debug-cluster/crictl/).
## kubeadm blocks when removing managed containers ## kubeadm blocks when removing managed containers
content/zh/docs/tasks/debug-application-cluster/debug-application-introspection.md
+1 -1
View File
@@ -1,4 +1,4 @@
--- :---
reviewers: reviewers:
- janetkuo - janetkuo
- thockin - thockin