Skip to content

Commit 83514e6

Browse files
Tim Bannistershannonxtreme
andauthored
Tweak page introduction
Co-authored-by: Shannon Kularathna <[email protected]>
1 parent b9a7ec6 commit 83514e6

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

content/en/docs/tasks/administer-cluster/migrating-from-dockershim/migrate-dockershim-dockerd.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,11 +7,13 @@ content_type: task
77
{{% thirdparty-content %}}
88

99
This page shows you how to migrate your Docker Engine nodes to use `cri-dockerd`
10-
instead of dockershim. If you want to switch away from using dockershim and still
11-
use Docker Engine to run containers in Kubernetes, you can follow these steps.
12-
If you want to upgrade to Kubernetes v{{< skew currentVersion >}} and your
13-
existing cluster relies on dockershim, you will have to migrate away and
14-
`cri-dockerd` is one of your options.
10+
instead of dockershim. You should follow these steps in these scenarios:
11+
12+
* You want to switch away from dockershim and still use Docker Engine to run
13+
containers in Kubernetes.
14+
* You want to upgrade to Kubernetes v{{< skew currentVersion >}} and your
15+
existing cluster relies on dockershim, in which case you must migrate
16+
from dockershim and `cri-dockerd` is one of your options.
1517

1618
To learn more about the removal of dockershim, read the [FAQ page](/dockershim).
1719

0 commit comments

Comments
 (0)