diff --git a/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/find-out-runtime-you-use.md b/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/find-out-runtime-you-use.md index 82c17dd80f..f6f3db70dd 100644 --- a/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/find-out-runtime-you-use.md +++ b/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/find-out-runtime-you-use.md @@ -41,9 +41,9 @@ node-2 Ready v1.16.15 docker://19.3.1 node-3 Ready v1.16.15 docker://19.3.1 ``` If your runtime shows as Docker Engine, you still might not be affected by the -removal of dockershim in Kubernetes v1.24. [Check the runtime -endpoint](#which-endpoint) to see if you use dockershim. If you don't use -dockershim, you aren't affected. +removal of dockershim in Kubernetes v1.24. +[Check the runtime endpoint](#which-endpoint) to see if you use dockershim. +If you don't use dockershim, you aren't affected. For containerd, the output is similar to this: @@ -97,4 +97,4 @@ nodes. If you want to change the Container Runtime on a Node from Docker Engine to containerd, you can find out more information on [migrating from Docker Engine to containerd](/docs/tasks/administer-cluster/migrating-from-dockershim/change-runtime-containerd/), or, if you want to continue using Docker Engine in Kubernetes v1.24 and later, migrate to a -CRI-compatible adapter like [`cri-dockerd`](https://github.com/Mirantis/cri-dockerd). \ No newline at end of file +CRI-compatible adapter like [`cri-dockerd`](https://github.com/Mirantis/cri-dockerd).