From 3b2495966a38070d68dbe7a3221d98e5bc4c13a6 Mon Sep 17 00:00:00 2001 From: Sebastiaan van Stijn Date: Mon, 12 Nov 2018 23:32:52 +0100 Subject: [PATCH 1/6] Update "select a storage driver" with current status The information on this page was a bit outdated, and with "overlay" and "devicemapper" being phased-out, could use some changes; - de-emphasize "overlay", "devicemapper" and "aufs" - split "recommended" and "alternative drivers" columns (vfs was listed as a "recommended" driver, but definitely is not recommended for production use). - add notes about "overlay" and "devicemapper" being deprecated in Docker 18.09 - some other textual changes. Signed-off-by: Sebastiaan van Stijn --- .../storagedriver/select-storage-driver.md | 87 +++++++++++-------- 1 file changed, 49 insertions(+), 38 deletions(-) diff --git a/storage/storagedriver/select-storage-driver.md b/storage/storagedriver/select-storage-driver.md index b2b957be0994..586c28006197 100644 --- a/storage/storagedriver/select-storage-driver.md +++ b/storage/storagedriver/select-storage-driver.md @@ -26,19 +26,27 @@ this decision, there are three high-level factors to consider: explicitly configured, assuming that the prerequisites for that storage driver are met: - - If possible, the storage driver with the least amount of configuration is - used, such as `btrfs` or `zfs`. Each of these relies on the backing - filesystem being configured correctly. - - - Otherwise, try to use the storage driver with the best overall performance - and stability in the most usual scenarios. - - - `overlay2` is preferred, followed by `overlay`. Neither of these requires - extra configuration. `overlay2` is the default choice for Docker CE. + - Try to use the storage driver with the best overall performance and stability + in the most usual scenarios. + - `overlay2` is the preferred storage driver, for all currently supported + Linux distributions, and requires no extra configuration. + - `aufs` is the preferred storage driver for Docker 18.06 and older, when + running on Ubuntu 14.04 on kernel 3.13 (which has no support for `overlay2`. - `devicemapper` is next, but requires `direct-lvm` for production environments, because `loopback-lvm`, while zero-configuration, has very - poor performance. + 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`, and + is now the recommended driver. + - The `btrfs` and `zfs` storage drivers are used if they are the backing + filesystem (the filesystem of the host on which Docker is installed). + These filesystems 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. + - 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 not generally recommended for production use. The selection order is defined in Docker's source code. You can see the order by looking at @@ -73,25 +81,34 @@ In addition, Docker does not recommend any configuration that requires you to disable security features of your operating system, such as the need to disable `selinux` if you use the `overlay` or `overlay2` driver on CentOS. -### Docker EE and CS-Engine +### Docker Engine Enterprise and Docker EE -For Docker EE and CS-Engine, the definitive resource for which storage drivers -are supported is the +For Docker Engine Enterprise and Docker EE, the definitive resource for which +storage drivers are supported is the [Product compatibility matrix](https://success.docker.com/Policies/Compatibility_Matrix). To get commercial support from Docker, you must use a supported configuration. -### Docker CE +### Docker Engine Community and Docker CE -For Docker CE, only some configurations are tested, and your operating system's -kernel may not support every storage driver. In general, the following +For Docker Engine Community, only some configurations are tested, and your operating +system's kernel may not support every storage driver. In general, the following configurations work on recent versions of the Linux distribution: -| Linux distribution | Recommended storage drivers | -|:--------------------|:------------------------------------------------------------------------------------------------------| -| Docker CE on Ubuntu | `aufs`, `devicemapper`, `overlay2` (Ubuntu 14.04.4 or later, 16.04 or later), `overlay`, `zfs`, `vfs` | -| Docker CE on Debian | `aufs`, `devicemapper`, `overlay2` (Debian Stretch), `overlay`, `vfs` | -| Docker CE on CentOS | `devicemapper`, `vfs` | -| Docker CE on Fedora | `devicemapper`, `overlay2` (Fedora 26 or later, experimental), `overlay` (experimental), `vfs` | +| Linux distribution | Recommended storage drivers | Alternative drivers | +|:--------------------|:-----------------------------------------------------------------------|:--------------------------------------------------| +| Docker CE on Ubuntu | `overlay2` or `aufs` (for Ubuntu 14.04 running on kernel 3.13) | `overlay`¹, `devicemapper`², `zfs`, `vfs` | +| Docker CE on Debian | `overlay2` (Debian Stretch), `aufs` or `devicemapper` (older versions) | `overlay`¹, `vfs` | +| Docker CE on CentOS | `overlay2` | `overlay`¹, `devicemapper`², `zfs`, `vfs` | +| Docker CE on Fedora | `overlay2` | `overlay`¹, `devicemapper`², `zfs`, `vfs` | + +¹) The `overlay` storage driver is marked deprecated in docker 18.09, and will be +removed in a future release. Users of the `overlay` storage driver are recommended +to migrate to `overlay2`. + +²) The `devicemapper` storage driver is marked deprecated in docker 18.09, and will be +removed in a future release. Users of the `devicemapper` storage driver are recommended +to migrate to `overlay2`. + When possible, `overlay2` is the recommended storage driver. When installing Docker for the first time, `overlay2` is used by default. Previously, `aufs` was @@ -140,12 +157,12 @@ backing filesystems. | Storage driver | Supported backing filesystems | |:----------------------|:------------------------------| -| `overlay`, `overlay2` | `ext4`, `xfs` | -| `aufs` | `ext4`, `xfs` | +| `overlay2`, `overlay` | `xfs` with fstype=1, `ext4` | +| `aufs` | `xfs`, `ext4` | | `devicemapper` | `direct-lvm` | | `btrfs` | `btrfs` | | `zfs` | `zfs` | - +| `vfs` | any filesystem | ## Other considerations @@ -155,13 +172,14 @@ Among other things, each storage driver has its own performance characteristics that make it more or less suitable for different workloads. Consider the following generalizations: -- `aufs`, `overlay`, and `overlay2` all operate at the file level rather than +- `overlay2`, `aufs`, and `overlay` all operate at the file level rather than the block level. This uses memory more efficiently, but the container's writable layer may grow quite large in write-heavy workloads. - Block-level storage drivers such as `devicemapper`, `btrfs`, and `zfs` perform better for write-heavy workloads (though not as well as Docker volumes). - For lots of small writes or containers with many layers or deep filesystems, - `overlay` may perform better than `overlay2`. + `overlay` may perform better than `overlay2`, but consumes more inodes, which + can lead to inode exhaustion. - `btrfs` and `zfs` require a lot of memory. - `zfs` is a good choice for high-density workloads such as PaaS. @@ -186,15 +204,8 @@ specific shared storage system. For some users, stability is more important than performance. Though Docker considers all of the storage drivers mentioned here to be stable, some are newer -and are still under active development. In general, `aufs`, `overlay`, and -`devicemapper` are the choices with the highest stability. - -### Experience and expertise - -Choose a storage driver that your organization is comfortable maintaining. For -example, if you use RHEL or one of its downstream forks, you may already have -experience with LVM and Device Mapper. If so, the `devicemapper` driver might -be the best choice. +and are still under active development. In general, `overlay2`, `aufs`, `overlay`, +and `devicemapper` are the choices with the highest stability. ### Test with your own workloads @@ -216,8 +227,8 @@ $ docker info Containers: 0 Images: 0 -Storage Driver: overlay - Backing Filesystem: extfs +Storage Driver: overlay2 + Backing Filesystem: xfs ``` From 48f9a7e09d3e6da4b134a495f1412b279561fe8c Mon Sep 17 00:00:00 2001 From: Anne Henmi <41210220+ahh-docker@users.noreply.github.com> Date: Tue, 13 Nov 2018 10:12:53 -0700 Subject: [PATCH 2/6] Update select-storage-driver.md --- .../storagedriver/select-storage-driver.md | 98 +++++++++---------- 1 file changed, 48 insertions(+), 50 deletions(-) diff --git a/storage/storagedriver/select-storage-driver.md b/storage/storagedriver/select-storage-driver.md index 586c28006197..eb075f528e79 100644 --- a/storage/storagedriver/select-storage-driver.md +++ b/storage/storagedriver/select-storage-driver.md @@ -21,56 +21,54 @@ After you have read the [storage driver overview](index.md), the next step is to choose the best storage driver for your workloads. In making this decision, there are three high-level factors to consider: -- If multiple storage drivers are supported in your kernel, Docker has a - prioritized list of which storage driver to use if no storage driver is - explicitly configured, assuming that the prerequisites for that storage driver - are met: - - - Try to use the storage driver with the best overall performance and stability - in the most usual scenarios. - - - `overlay2` is the preferred storage driver, for all currently supported - Linux distributions, and requires no extra configuration. - - `aufs` is the preferred storage driver for Docker 18.06 and older, when - running on Ubuntu 14.04 on kernel 3.13 (which has no support for `overlay2`. - - `devicemapper` is next, but 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`, and - is now the recommended driver. - - The `btrfs` and `zfs` storage drivers are used if they are the backing - filesystem (the filesystem of the host on which Docker is installed). - These filesystems 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. - - 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 not generally recommended for production use. - - The selection order is defined in Docker's source code. You can see the order - by looking at - [the source code for Docker CE {{ site.docker_ce_stable_version }}](https://github.com/docker/docker-ce/blob/{{ site.docker_ce_stable_version }}/components/engine/daemon/graphdriver/driver_linux.go#L50) - You can use the branch selector at the top of the file viewer to choose a - different branch, if you run a different version of Docker. - {: id="storage-driver-order" } - -- Your choice may be limited by your Docker edition, operating system, and - distribution. For instance, `aufs` is only supported on Ubuntu and Debian, and - may require extra packages to be installed, - while `btrfs` is only supported on SLES, which is only supported with Docker - EE. See - [Support storage drivers per Linux distribution](#supported-storage-drivers-per-linux-distribution). - -- Some storage drivers require you to use a specific format for the backing - filesystem. If you have external requirements to use a specific backing - filesystem, this may limit your choices. See - [Supported backing filesystems](#supported-backing-filesystems). - -- After you have narrowed down which storage drivers you can choose from, your - choice are determined by the characteristics of your workload and the - level of stability you need. See [Other considerations](#other-considerations) - for help making the final decision. +If multiple storage drivers are supported in your kernel, Docker has prioritized +list of which storage driver to use if no storage driver is explicitly configured, +assuming that the that storage driver meets the prerequisites. + +Use the storage driver with the best overall performance and stability in the most +usual scenarios. + +Docker supports the following storage drivers: + +* `overlay2` is the preferred storage driver, for all currently supported + Linux distributions, and requires no extra configuration. +* `aufs` is the preferred storage driver for Docker 18.06 and older, when + running on Ubuntu 14.04 on kernel 3.13 (which has no support for `overlay2`. +* `devicemapper` is supported, but 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`, and + is now the recommended driver. + * The `btrfs` and `zfs` storage drivers are used if they are the backing + filesystem (the filesystem of the host on which Docker is installed). + These filesystems 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. + * 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 not generally recommended for production use. + +Docker's source code defines the selection order. You can see the order at +[the source code for Docker CE {{ site.docker_ce_stable_version }}](https://github.com/docker/docker-ce/blob/{{ site.docker_ce_stable_version }}/components/engine/daemon/graphdriver/driver_linux.go#L50) + +You can use the branch selector at the top of the file viewer to choose a different branch, if you run a +different version of Docker. +{: id="storage-driver-order" } + +Some storage drivers require you to use a specific format for the backing filesystem. If you have external +requirements to use a specific backing filesystem, this may limit your choices. See [Supported backing filesystems](#supported-backing-filesystems). + +After you have narrowed down which storage drivers you can choose from, your choice are determined by the +characteristics of your workload and the level of stability you need. See [Other considerations](#other-considerations) +for help making the final decision. + +> ***NOTE***: Your choice may be limited by your Docker edition, operating system, and distribution. +> For instance, `aufs` is only supported on Ubuntu and Debian, and may require extra packages +> to be installed, while `btrfs` is only supported on SLES, which is only supported with Docker +> EE. See [Support storage drivers per Linux distribution](#supported-storage-drivers-per-linux-distribution) +> for more information. + ## Supported storage drivers per Linux distribution From f0c93ff9682637b412968598637d0a312a737215 Mon Sep 17 00:00:00 2001 From: Anne Henmi <41210220+ahh-docker@users.noreply.github.com> Date: Tue, 13 Nov 2018 11:45:01 -0700 Subject: [PATCH 3/6] Update select-storage-driver.md --- storage/storagedriver/select-storage-driver.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/storage/storagedriver/select-storage-driver.md b/storage/storagedriver/select-storage-driver.md index eb075f528e79..3d3dbdefcda8 100644 --- a/storage/storagedriver/select-storage-driver.md +++ b/storage/storagedriver/select-storage-driver.md @@ -21,7 +21,7 @@ After you have read the [storage driver overview](index.md), the next step is to choose the best storage driver for your workloads. In making this decision, there are three high-level factors to consider: -If multiple storage drivers are supported in your kernel, Docker has prioritized +If multiple storage drivers are supported in your kernel, Docker has a prioritized list of which storage driver to use if no storage driver is explicitly configured, assuming that the that storage driver meets the prerequisites. @@ -39,7 +39,7 @@ Docker supports the following storage drivers: 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`, and - is now the recommended driver. + which is now the recommended driver. * The `btrfs` and `zfs` storage drivers are used if they are the backing filesystem (the filesystem of the host on which Docker is installed). These filesystems allow for advanced options, such as creating "snapshots", From 3d7a90acb199d5d087c5334dce5ff7beec410a85 Mon Sep 17 00:00:00 2001 From: Maria Bermudez Date: Tue, 13 Nov 2018 11:05:43 -0800 Subject: [PATCH 4/6] Minor edits --- .../storagedriver/select-storage-driver.md | 27 +++++++++---------- 1 file changed, 13 insertions(+), 14 deletions(-) diff --git a/storage/storagedriver/select-storage-driver.md b/storage/storagedriver/select-storage-driver.md index 3d3dbdefcda8..0426566651cc 100644 --- a/storage/storagedriver/select-storage-driver.md +++ b/storage/storagedriver/select-storage-driver.md @@ -23,7 +23,7 @@ this decision, there are three high-level factors to consider: If multiple storage drivers are supported in your kernel, Docker has a prioritized list of which storage driver to use if no storage driver is explicitly configured, -assuming that the that storage driver meets the prerequisites. +assuming that the storage driver meets the prerequisites. Use the storage driver with the best overall performance and stability in the most usual scenarios. @@ -33,12 +33,12 @@ Docker supports the following storage drivers: * `overlay2` is the preferred storage driver, for all currently supported Linux distributions, and requires no extra configuration. * `aufs` is the preferred storage driver for Docker 18.06 and older, when - running on Ubuntu 14.04 on kernel 3.13 (which has no support for `overlay2`. + running on Ubuntu 14.04 on kernel 3.13 which has no support for `overlay2`. * `devicemapper` is supported, but 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`, and + current versions of CentOS and RHEL now have support for `overlay2`, which is now the recommended driver. * The `btrfs` and `zfs` storage drivers are used if they are the backing filesystem (the filesystem of the host on which Docker is installed). @@ -47,21 +47,20 @@ Docker supports the following storage drivers: filesystem being configured correctly. * 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 not generally recommended for production use. + driver is poor, and is not generally recommended for production use. Docker's source code defines the selection order. You can see the order at [the source code for Docker CE {{ site.docker_ce_stable_version }}](https://github.com/docker/docker-ce/blob/{{ site.docker_ce_stable_version }}/components/engine/daemon/graphdriver/driver_linux.go#L50) -You can use the branch selector at the top of the file viewer to choose a different branch, if you run a -different version of Docker. +If you run a different version of Docker, you can use the branch selector at the top of the file viewer to choose a different branch. {: id="storage-driver-order" } Some storage drivers require you to use a specific format for the backing filesystem. If you have external requirements to use a specific backing filesystem, this may limit your choices. See [Supported backing filesystems](#supported-backing-filesystems). -After you have narrowed down which storage drivers you can choose from, your choice are determined by the +After you have narrowed down which storage drivers you can choose from, your choice is determined by the characteristics of your workload and the level of stability you need. See [Other considerations](#other-considerations) -for help making the final decision. +for help in making the final decision. > ***NOTE***: Your choice may be limited by your Docker edition, operating system, and distribution. > For instance, `aufs` is only supported on Ubuntu and Debian, and may require extra packages @@ -99,13 +98,13 @@ configurations work on recent versions of the Linux distribution: | Docker CE on CentOS | `overlay2` | `overlay`¹, `devicemapper`², `zfs`, `vfs` | | Docker CE on Fedora | `overlay2` | `overlay`¹, `devicemapper`², `zfs`, `vfs` | -¹) The `overlay` storage driver is marked deprecated in docker 18.09, and will be -removed in a future release. Users of the `overlay` storage driver are recommended -to migrate to `overlay2`. +¹) The `overlay` storage driver is deprecated in Docker 18.09, and will be +removed in a future release. It is recommended that users of the `overlay` storage driver +migrate to `overlay2`. -²) The `devicemapper` storage driver is marked deprecated in docker 18.09, and will be -removed in a future release. Users of the `devicemapper` storage driver are recommended -to migrate to `overlay2`. +²) The `devicemapper` storage driver is deprecated in Docker 18.09, and will be +removed in a future release. It is recommended that users of the `overlay` storage driver +migrate to `overlay2`. When possible, `overlay2` is the recommended storage driver. When installing From e7cbb509230708f82b7827c2a229410fe067351a Mon Sep 17 00:00:00 2001 From: Anne Henmi <41210220+ahh-docker@users.noreply.github.com> Date: Tue, 13 Nov 2018 12:45:59 -0700 Subject: [PATCH 5/6] Update select-storage-driver.md --- storage/storagedriver/select-storage-driver.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/storage/storagedriver/select-storage-driver.md b/storage/storagedriver/select-storage-driver.md index 0426566651cc..cfeb1b6b82c5 100644 --- a/storage/storagedriver/select-storage-driver.md +++ b/storage/storagedriver/select-storage-driver.md @@ -98,7 +98,7 @@ configurations work on recent versions of the Linux distribution: | Docker CE on CentOS | `overlay2` | `overlay`¹, `devicemapper`², `zfs`, `vfs` | | Docker CE on Fedora | `overlay2` | `overlay`¹, `devicemapper`², `zfs`, `vfs` | -¹) The `overlay` storage driver is deprecated in Docker 18.09, and will be +¹) The `overlay` storage driver is deprecated in Docker Engine - Enterprise 18.09, and will be removed in a future release. It is recommended that users of the `overlay` storage driver migrate to `overlay2`. From 3805b23d93159761b9a08d7dbb2c68d3afe7113f Mon Sep 17 00:00:00 2001 From: Anne Henmi <41210220+ahh-docker@users.noreply.github.com> Date: Tue, 13 Nov 2018 13:20:33 -0700 Subject: [PATCH 6/6] Update select-storage-driver.md Fixed product naming --- .../storagedriver/select-storage-driver.md | 28 +++++++++---------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/storage/storagedriver/select-storage-driver.md b/storage/storagedriver/select-storage-driver.md index cfeb1b6b82c5..f6655101be17 100644 --- a/storage/storagedriver/select-storage-driver.md +++ b/storage/storagedriver/select-storage-driver.md @@ -50,7 +50,7 @@ Docker supports the following storage drivers: driver is poor, and is not generally recommended for production use. Docker's source code defines the selection order. You can see the order at -[the source code for Docker CE {{ site.docker_ce_stable_version }}](https://github.com/docker/docker-ce/blob/{{ site.docker_ce_stable_version }}/components/engine/daemon/graphdriver/driver_linux.go#L50) +[the source code for Docker Engine - Community {{ site.docker_ce_stable_version }}](https://github.com/docker/docker-ce/blob/{{ site.docker_ce_stable_version }}/components/engine/daemon/graphdriver/driver_linux.go#L50) If you run a different version of Docker, you can use the branch selector at the top of the file viewer to choose a different branch. {: id="storage-driver-order" } @@ -65,7 +65,7 @@ for help in making the final decision. > ***NOTE***: Your choice may be limited by your Docker edition, operating system, and distribution. > For instance, `aufs` is only supported on Ubuntu and Debian, and may require extra packages > to be installed, while `btrfs` is only supported on SLES, which is only supported with Docker -> EE. See [Support storage drivers per Linux distribution](#supported-storage-drivers-per-linux-distribution) +> Enterprise. See [Support storage drivers per Linux distribution](#supported-storage-drivers-per-linux-distribution) > for more information. @@ -78,31 +78,31 @@ In addition, Docker does not recommend any configuration that requires you to disable security features of your operating system, such as the need to disable `selinux` if you use the `overlay` or `overlay2` driver on CentOS. -### Docker Engine Enterprise and Docker EE +### Docker Engine - Enterprise and Docker Enterprise -For Docker Engine Enterprise and Docker EE, the definitive resource for which +For Docker Engine - Enterprise and Docker Enterprise, the definitive resource for which storage drivers are supported is the [Product compatibility matrix](https://success.docker.com/Policies/Compatibility_Matrix). To get commercial support from Docker, you must use a supported configuration. -### Docker Engine Community and Docker CE +### Docker Engine - Community -For Docker Engine Community, only some configurations are tested, and your operating +For Docker Engine - Community, only some configurations are tested, and your operating system's kernel may not support every storage driver. In general, the following configurations work on recent versions of the Linux distribution: | Linux distribution | Recommended storage drivers | Alternative drivers | |:--------------------|:-----------------------------------------------------------------------|:--------------------------------------------------| -| Docker CE on Ubuntu | `overlay2` or `aufs` (for Ubuntu 14.04 running on kernel 3.13) | `overlay`¹, `devicemapper`², `zfs`, `vfs` | -| Docker CE on Debian | `overlay2` (Debian Stretch), `aufs` or `devicemapper` (older versions) | `overlay`¹, `vfs` | -| Docker CE on CentOS | `overlay2` | `overlay`¹, `devicemapper`², `zfs`, `vfs` | -| Docker CE on Fedora | `overlay2` | `overlay`¹, `devicemapper`², `zfs`, `vfs` | +| Docker Engine - Community on Ubuntu | `overlay2` or `aufs` (for Ubuntu 14.04 running on kernel 3.13) | `overlay`¹, `devicemapper`², `zfs`, `vfs` | +| Docker Engine - Community on Debian | `overlay2` (Debian Stretch), `aufs` or `devicemapper` (older versions) | `overlay`¹, `vfs` | +| Docker Engine - Community on CentOS | `overlay2` | `overlay`¹, `devicemapper`², `zfs`, `vfs` | +| Docker Engine - Community on Fedora | `overlay2` | `overlay`¹, `devicemapper`², `zfs`, `vfs` | ¹) The `overlay` storage driver is deprecated in Docker Engine - Enterprise 18.09, and will be removed in a future release. It is recommended that users of the `overlay` storage driver migrate to `overlay2`. -²) The `devicemapper` storage driver is deprecated in Docker 18.09, and will be +²) The `devicemapper` storage driver is deprecated in Docker Engine 18.09, and will be removed in a future release. It is recommended that users of the `overlay` storage driver migrate to `overlay2`. @@ -126,10 +126,10 @@ storage driver, be sure to read about [its performance and storage characteristics and limitations](vfs-driver.md). > **Expectations for non-recommended storage drivers**: Commercial support is -> not available for Docker CE, and you can technically use any storage driver +> not available for Docker Engine - Community, and you can technically use any storage driver > that is available for your platform. For instance, you can use `btrfs` with -> Docker CE, even though it is not recommended on any platform for Docker CE, -> and you do so at your own risk. +> Docker Engine - Community, even though it is not recommended on any platform for +> Docker Engine - Community, and you do so at your own risk. > > The recommendations in the table above are based on automated regression > testing and the configurations that are known to work for a large number of