Skip to content

Commit 65e92a8

Browse files
Tim Bannisterreylejano
andcommitted
Add Docker Engine as container runtime
Mention that the support via Dockershim is deprecated. Co-Authored-By: Rey Lejano <[email protected]>
1 parent 6d9fec4 commit 65e92a8

File tree

1 file changed

+34
-0
lines changed

1 file changed

+34
-0
lines changed

content/en/docs/setup/production-environment/container-runtimes.md

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,11 +15,18 @@ what is involved and describes related tasks for setting up nodes.
1515

1616
<!-- body -->
1717

18+
Kubernetes {{< skew currentVersion >}} requires that you use a runtime that
19+
conforms with the
20+
{{< glossary_tooltip term_id="cri" text="Container Runtime Interface">}} (CRI).
21+
22+
See [CRI version support](#cri-versions) for more information.
23+
1824
This page lists details for using several common container runtimes with
1925
Kubernetes, on Linux:
2026

2127
- [containerd](#containerd)
2228
- [CRI-O](#cri-o)
29+
- [Docker Engine](#docker)
2330
- [Mirantis Container Runtime](#mcr)
2431

2532
{{< note >}}
@@ -94,10 +101,19 @@ In order to use it, cgroup v2 must be supported by the CRI runtime as well.
94101
Follow this [Migration guide](/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver/)
95102
if you wish to migrate to the `systemd` cgroup driver in existing kubeadm managed clusters.
96103

104+
## CRI version support {#cri-versions}
105+
106+
Your container runtime must support at least v1alpha2 of the container runtime interface.
107+
108+
Kubernetes {{< skew currentVersion >}} defaults to using v1 of the CRI API.
109+
If a container runtime does not support the v1 API, the kubelet falls back to
110+
using the (deprecated) v1alpha2 API instead.
111+
97112
## Container runtimes
98113

99114
{{% thirdparty-content %}}
100115

116+
101117
### containerd
102118

103119
This section contains the necessary steps to use containerd as CRI runtime.
@@ -394,6 +410,24 @@ Please also note the changed `conmon_cgroup`, which has to be set to the value
394410
cgroup driver configuration of the kubelet (usually done via kubeadm) and CRI-O
395411
in sync.
396412

413+
### Docker Engine {#docker}
414+
415+
Docker Engine is the container runtime that started it all. Formerly known just as Docker,
416+
this container runtime is available in various forms.
417+
[Install Docker Engine](https://docs.docker.com/engine/install/) explains your options
418+
for installing this runtime.
419+
420+
Docker Engine is directly compatible with Kubernetes {{< skew currentVersion >}}, using the deprecated `dockershim` component. For more information
421+
and context, see the [Dockershim deprecation FAQ](/dockershim).
422+
423+
You can also find third-party adapters that let you use Docker Engine with Kubernetes
424+
through the supported {{< glossary_tooltip term_id="cri" text="Container Runtime Interface">}}
425+
(CRI).
426+
427+
The following CRI adaptors are designed to work with Docker Engine:
428+
429+
- [`cri-dockerd`](https://github.com/Mirantis/cri-dockerd) from Mirantis
430+
397431
### Mirantis Container Runtime {#mcr}
398432

399433
[Mirantis Container Runtime](https://docs.mirantis.com/mcr/20.10/overview.html) (MCR) is a commercially

0 commit comments

Comments
 (0)