From cc3ba5be2c0792ff721f32ed9bfd366271b55ae9 Mon Sep 17 00:00:00 2001 From: John Huang <616672335@qq.com> Date: Mon, 16 Oct 2023 02:38:55 +0800 Subject: [PATCH] Fix stale advice on changing the Container Runtime on a Node (#42739) * Stale advice on changing the Container Runtime on a Node from Docker Engine to containerd * Update content/en/docs/tasks/administer-cluster/migrating-from-dockershim/migrate-dockershim-dockerd.md Co-authored-by: Tim Bannister * Update migrate-dockershim-dockerd.md --------- Co-authored-by: Tim Bannister --- .../migrating-from-dockershim/migrate-dockershim-dockerd.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/migrate-dockershim-dockerd.md b/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/migrate-dockershim-dockerd.md index 9bbba039e0d9c..a4adb12234622 100644 --- a/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/migrate-dockershim-dockerd.md +++ b/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/migrate-dockershim-dockerd.md @@ -76,6 +76,8 @@ instructions for that tool. 1. Open `/var/lib/kubelet/kubeadm-flags.env` on each affected node. 1. Modify the `--container-runtime-endpoint` flag to `unix:///var/run/cri-dockerd.sock`. +1. Modify the `--container-runtime` flag to `remote` + (unavailable in Kubernetes v1.27 and later). The kubeadm tool stores the node's socket as an annotation on the `Node` object in the control plane. To modify this socket for each affected node: @@ -118,4 +120,4 @@ kubectl uncordon ## {{% heading "whatsnext" %}} * Read the [dockershim removal FAQ](/dockershim/). -* [Learn how to migrate from Docker Engine with dockershim to containerd](/docs/tasks/administer-cluster/migrating-from-dockershim/change-runtime-containerd/). \ No newline at end of file +* [Learn how to migrate from Docker Engine with dockershim to containerd](/docs/tasks/administer-cluster/migrating-from-dockershim/change-runtime-containerd/).