From 63aabb9962f48dc3fd869199a2cf4353f6f8c4dc Mon Sep 17 00:00:00 2001 From: Thilo Fromm Date: Mon, 30 Oct 2023 18:03:27 +0100 Subject: [PATCH] chagelog: update docker btrfs backwards compatibility --- changelog/changes/2023-10-25-docker-gentoo-upstream.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/changelog/changes/2023-10-25-docker-gentoo-upstream.md b/changelog/changes/2023-10-25-docker-gentoo-upstream.md index 9320f364ca..0f80ccdfd0 100644 --- a/changelog/changes/2023-10-25-docker-gentoo-upstream.md +++ b/changelog/changes/2023-10-25-docker-gentoo-upstream.md @@ -2,5 +2,5 @@ - **NOTE** The docker btrfs storage driver has been de-prioritised; BTRFS backed storage will now default to the `overlay2` driver ([changelog](https://docs.docker.com/engine/release-notes/23.0/#bug-fixes-and-enhancements-6), [upstream pr](https://github.com/moby/moby/pull/42661)). Using the btrfs driver can still be enforced by creating a respective [docker config](https://docs.docker.com/storage/storagedriver/btrfs-driver/#configure-docker-to-use-the-btrfs-storage-driver) at `/etc/docker/daemon.json`. - - **NOTE that if you are using btrfs-backed Docker storage and are upgrading to this new version then the driver for that storage will change to `overlay2`.** - To prevent this please create a respective docker daemon configuration file on affected nodes as discussed above. + - **NOTE** that if you are already using btrfs-backed Docker storage and are upgrading to this new version, Docker will automatically use the `btrfs` storage driver for backwards-compatibility with your deployment. + - **Docker will remove the `btrfs` driver entirely in a future version. Please consider migrating your deployments to the `overlay2` driver.**