From 0c5e5622f49abde73b24332b61ac01248700b8db Mon Sep 17 00:00:00 2001 From: Misty Stanley-Jones Date: Fri, 20 Oct 2017 10:14:58 -0700 Subject: [PATCH] Make it more clear that you probably don't need to configure btrfs (#5049) --- engine/installation/linux/docker-ee/suse.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/engine/installation/linux/docker-ee/suse.md b/engine/installation/linux/docker-ee/suse.md index 92b4570e6a..c499aefe05 100644 --- a/engine/installation/linux/docker-ee/suse.md +++ b/engine/installation/linux/docker-ee/suse.md @@ -65,14 +65,18 @@ networks, are preserved. The Docker EE package is now called `docker-ee`. ## Configure the btrfs filesystem -By default, SLES formats the `/` filesystem using BTRFS. If the filesystem which +By default, SLES formats the `/` filesystem using BTRFS, so **most people do not +not need to do the steps in this section**. If the filesystem that hosts `/var/lib/docker/` is **not** a BTRFS filesystem, you must configure a BTRFS filesystem and mount it on `/var/lib/docker/`: 1. Format your dedicated block device or devices as a Btrfs filesystem. This example assumes that you are using two block devices called `/dev/xvdf` and - `/dev/xvdg`. Double-check the block device names because this is a + `/dev/xvdg`. + + > Double-check the block device names because this is a destructive operation. + {:.warning} ```bash $ sudo mkfs.btrfs -f /dev/xvdf /dev/xvdg