docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update btrfs-driver.md (#1963) 

It seems that some word is missing. Added a "for".
This commit is contained in:
Wang Jie 2017-02-28 14:38:22 +08:00 committed by John Mulhausen
parent b035953c9e
commit cd410b5cee
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
engine/userguide/storagedriver/btrfs-driver.md
View File

@ -17,7 +17,7 @@ copy-on-write, and snapshotting.
This article refers to Docker's Btrfs storage driver as `btrfs` and the overall
Btrfs Filesystem as Btrfs.
>**Note**: The [Commercially Supported Docker Engine (CS-Engine)](https://www.docker.com/compatibility-maintenance) does not currently support the `btrfs` storage driver.
> **Note:** The [Commercially Supported Docker Engine (CS-Engine)](https://www.docker.com/compatibility-maintenance) does not currently support the `btrfs` storage driver.
## The future of Btrfs
@ -102,7 +102,7 @@ that as Btrfs filesystem objects and not as individual mounts.
Because Btrfs works at the filesystem level and not the block level, each image
and container layer can be browsed in the filesystem using normal Unix
commands. The example below shows a truncated output of an `ls -l` command an
commands. The example below shows a truncated output of an `ls -l` command for an
image layer:
$ ls -l /var/lib/docker/btrfs/subvolumes/0a17decee4139b0de68478f149cc16346f5e711c5ae3bb969895f22dd6723751/
@ -194,7 +194,7 @@ multiple devices to the `mkfs.btrfs` command creates a pool across all of those
Be sure to substitute `/dev/xvdb` with the appropriate device(s) on your
system.
> **Warning**: Take note of the warning about Btrfs being experimental. As
> **Warning:** Take note of the warning about Btrfs being experimental. As
noted earlier, Btrfs is not currently recommended for production deployments
unless you already have extensive experience.