mirror of https://github.com/docker/docs.git
engine: describe how to use the c8d image store with docker-ce
Signed-off-by: David Karlsson <david.karlsson@docker.com>
This commit is contained in:
parent
98a3a218db
commit
53b11a8487
|
@ -1346,6 +1346,8 @@ manuals:
|
|||
title: Use the VFS storage driver
|
||||
- path: /storage/storagedriver/aufs-driver/
|
||||
title: Use the AUFS storage driver (deprecated)
|
||||
- path: /storage/containerd/
|
||||
title: containerd snapshotters
|
||||
- sectiontitle: Networking
|
||||
section:
|
||||
- path: /network/
|
||||
|
|
|
@ -0,0 +1,58 @@
|
|||
---
|
||||
title: containerd image store with Docker Engine
|
||||
keywords: containerd, snapshotters, image store, docker engine
|
||||
description: Enabling the containerd image store on Docker Engine
|
||||
---
|
||||
|
||||
> **Note**
|
||||
>
|
||||
> The containerd image store is an experimental feature of Docker Engine.
|
||||
> If you're using Docker Desktop, don't use the instructions on this page. See
|
||||
> [containerd image store with Docker Desktop](../desktop/containerd/index.md).
|
||||
|
||||
containerd, the industry-standard container runtime, uses snapshotters instead
|
||||
of the classic storage drivers for storing image and container data.
|
||||
While the `overlay2` driver still remains the default driver for Docker Engine,
|
||||
you can opt in to using containerd snapshotters as an experimental feature.
|
||||
|
||||
To learn more about the containerd image store and its benefits, refer to
|
||||
[containerd image store on Docker Desktop](../desktop/containerd/index.md).
|
||||
|
||||
## Enable containerd image store on Docker Engine
|
||||
|
||||
Switching to containerd snapshotters causes you to temporarily lose images and
|
||||
containers created using the classic storage drivers.
|
||||
Those resources still exist on your filesystem, and you can retrieve them by
|
||||
turning off the containerd snapshotters feature.
|
||||
|
||||
The following steps explain how to enable the containerd snapshotters feature.
|
||||
|
||||
1. Add the following configuration to your `/etc/docker/daemon.json`
|
||||
configuration file:
|
||||
|
||||
```json
|
||||
{
|
||||
"features": {
|
||||
"containerd-snapshotter": true
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
2. Save the file.
|
||||
3. Restart the daemon for the changes to take effect.
|
||||
|
||||
```console
|
||||
$ sudo systemctl restart docker
|
||||
```
|
||||
|
||||
After restarting the daemon, running `docker info` shows that you're using
|
||||
containerd snapshotter storage drivers.
|
||||
|
||||
{% raw %}
|
||||
```console
|
||||
$ docker info -f '{{ .DriverStatus }}'
|
||||
[[driver-type io.containerd.snapshotter.v1]]
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
Docker Engine uses the `overlayfs` containerd snapshotter by default.
|
Loading…
Reference in New Issue