Update kubeadm CRI detection docs
Update kubeadm CRI detection docs in light of dockershim deprecation. Co-authored-by: Lubomir I. Ivanov <neolit123@gmail.com>
This commit is contained in:
@@ -93,30 +93,30 @@ to interface with your chosen container runtime.
|
|||||||
|
|
||||||
If you don't specify a runtime, kubeadm automatically tries to detect an installed
|
If you don't specify a runtime, kubeadm automatically tries to detect an installed
|
||||||
container runtime by scanning through a list of well known Unix domain sockets.
|
container runtime by scanning through a list of well known Unix domain sockets.
|
||||||
The following table lists container runtimes and their associated socket paths:
|
The following table lists container runtimes that kubeadm looks for, and their associated socket paths:
|
||||||
|
|
||||||
{{< table caption = "Container runtimes and their socket paths" >}}
|
{{< table caption = "Container runtimes and their socket paths" >}}
|
||||||
| Runtime | Path to Unix domain socket |
|
| Runtime | Path to Unix domain socket |
|
||||||
|------------|-----------------------------------|
|
|----------------|-----------------------------------|
|
||||||
| Docker | `/var/run/dockershim.sock` |
|
| Docker Engine | `/var/run/dockershim.sock` |
|
||||||
| containerd | `/run/containerd/containerd.sock` |
|
| containerd | `/run/containerd/containerd.sock` |
|
||||||
| CRI-O | `/var/run/crio/crio.sock` |
|
| CRI-O | `/var/run/crio/crio.sock` |
|
||||||
{{< /table >}}
|
{{< /table >}}
|
||||||
|
|
||||||
<br />
|
<br />
|
||||||
If both Docker and containerd are detected, Docker takes precedence. This is
|
If both Docker Engine and containerd are detected, kubeadm will give precedence to Docker Engine. This is
|
||||||
needed because Docker 18.09 ships with containerd and both are detectable even if you only
|
needed because Docker 18.09 ships with containerd and both are detectable even if you only
|
||||||
installed Docker.
|
installed Docker.
|
||||||
If any other two or more runtimes are detected, kubeadm exits with an error.
|
**If any other two or more runtimes are detected, kubeadm exits with an error.**
|
||||||
|
|
||||||
The kubelet integrates with Docker through the built-in `dockershim` CRI implementation.
|
The kubelet can integrate with Docker Engine using the deprecated `dockershim` adapter (the dockershim is part of the kubelet itself).
|
||||||
|
|
||||||
See [container runtimes](/docs/setup/production-environment/container-runtimes/)
|
See [container runtimes](/docs/setup/production-environment/container-runtimes/)
|
||||||
for more information.
|
for more information.
|
||||||
{{% /tab %}}
|
{{% /tab %}}
|
||||||
{{% tab name="other operating systems" %}}
|
{{% tab name="other operating systems" %}}
|
||||||
By default, kubeadm uses {{< glossary_tooltip term_id="docker" >}} as the container runtime.
|
By default, kubeadm uses {{< glossary_tooltip term_id="docker" >}} as the container runtime.
|
||||||
The kubelet integrates with Docker through the built-in `dockershim` CRI implementation.
|
The kubelet can integrate with Docker Engine using the deprecated `dockershim` adapter (the dockershim is part of the kubelet itself).
|
||||||
|
|
||||||
See [container runtimes](/docs/setup/production-environment/container-runtimes/)
|
See [container runtimes](/docs/setup/production-environment/container-runtimes/)
|
||||||
for more information.
|
for more information.
|
||||||
|
|||||||
Reference in New Issue
Block a user