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

[en] update url 

Signed-off-by: xin.li <xin.li@daocloud.io>
This commit is contained in:
xin.li 2022-05-15 19:35:01 +08:00
parent bf46c15bdf
commit b7fe7cfa94
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/en/blog/_posts/2022-02-17-updated-dockershim-faq.md
View File

@ -175,7 +175,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 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)) [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], and for the 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.

2
content/en/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm.md
View File

@ -114,7 +114,7 @@ sudo kubeadm reset
A possible solution is to restart the container runtime and then re-run `kubeadm reset`. A possible solution is to restart the container runtime and then re-run `kubeadm reset`.
You can also use `crictl` to debug the state of the container runtime. See You can also use `crictl` to debug the state of the 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/).
## Pods in `RunContainerError`, `CrashLoopBackOff` or `Error` state ## Pods in `RunContainerError`, `CrashLoopBackOff` or `Error` state