From c3cad2a3fd491358e3f637f90b2b589dc633ecb8 Mon Sep 17 00:00:00 2001 From: Sebastiaan van Stijn Date: Wed, 13 Dec 2023 09:45:18 +0100 Subject: [PATCH] storage-drivers: add warning about devicemapper deprecation Signed-off-by: Sebastiaan van Stijn --- content/storage/storagedriver/device-mapper-driver.md | 11 ++++++++++- .../storage/storagedriver/select-storage-driver.md | 2 +- 2 files changed, 11 insertions(+), 2 deletions(-) diff --git a/content/storage/storagedriver/device-mapper-driver.md b/content/storage/storagedriver/device-mapper-driver.md index 961b9be430..bcae776043 100644 --- a/content/storage/storagedriver/device-mapper-driver.md +++ b/content/storage/storagedriver/device-mapper-driver.md @@ -1,11 +1,20 @@ --- description: Learn how to optimize your use of device mapper driver. keywords: container, storage, driver, device mapper -title: Use the Device Mapper storage driver +title: Use the Device Mapper storage driver (deprecated) aliases: - /engine/userguide/storagedriver/device-mapper-driver/ --- +> **Deprecated** +> +> The Device Mapper driver [has been deprecated](../../../engine/deprecated.md#device-mapper-storage-driver), +> and will be removed in Docker Engine v25.0. If you are using Device Mapper, +> you must migrate to a supported storage driver before upgrading to Docker +> Engine v25.0. Read the [Docker storage drivers](select-storage-driver.md) +> page for supported storage drivers. +{ .warning } + Device Mapper is a kernel-based framework that underpins many advanced volume management technologies on Linux. Docker's `devicemapper` storage driver leverages the thin provisioning and snapshotting capabilities of this framework diff --git a/content/storage/storagedriver/select-storage-driver.md b/content/storage/storagedriver/select-storage-driver.md index 02ff26fb96..49acee97e6 100644 --- a/content/storage/storagedriver/select-storage-driver.md +++ b/content/storage/storagedriver/select-storage-driver.md @@ -27,7 +27,7 @@ The Docker Engine provides the following storage drivers on Linux: | `fuse-overlayfs` | `fuse-overlayfs`is preferred only for running Rootless Docker on a host that does not provide support for rootless `overlay2`. On Ubuntu and Debian 10, the `fuse-overlayfs` driver does not need to be used, and `overlay2` works even in rootless mode. Refer to the [rootless mode documentation](../../engine/security/rootless.md) for details. | | `btrfs` and `zfs` | The `btrfs` and `zfs` storage drivers allow for advanced options, such as creating "snapshots", but require more maintenance and setup. Each of these relies on the backing filesystem being configured correctly. | | `vfs` | The `vfs` storage driver is intended for testing purposes, and for situations where no copy-on-write filesystem can be used. Performance of this storage driver is poor, and is not generally recommended for production use. | -| `devicemapper` | The `devicemapper` storage driver requires `direct-lvm` for production environments, because `loopback-lvm`, while zero-configuration, has very poor performance. `devicemapper` was the recommended storage driver for CentOS and RHEL, as their kernel version did not support `overlay2`. However, current versions of CentOS and RHEL now have support for `overlay2`, which is now the recommended driver. | +| `devicemapper` ([deprecated](../../../engine/deprecated.md#device-mapper-storage-driver)) | The `devicemapper` storage driver requires `direct-lvm` for production environments, because `loopback-lvm`, while zero-configuration, has very poor performance. `devicemapper` was the recommended storage driver for CentOS and RHEL, as their kernel version did not support `overlay2`. However, current versions of CentOS and RHEL now have support for `overlay2`, which is now the recommended driver. |