From b951eb79dbf892feb3155e619f7b58e1d65cf067 Mon Sep 17 00:00:00 2001 From: Deng Guangxing Date: Wed, 11 Mar 2015 11:13:39 +0800 Subject: [PATCH] Fix minor typo Signed-off-by: Deng Guangxing Upstream-commit: ce1a0b612d300210fadf12556e1b38885f098197 Component: engine --- components/engine/daemon/graphdriver/devmapper/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/components/engine/daemon/graphdriver/devmapper/README.md b/components/engine/daemon/graphdriver/devmapper/README.md index 30e63f7ab2..1dc918016d 100644 --- a/components/engine/daemon/graphdriver/devmapper/README.md +++ b/components/engine/daemon/graphdriver/devmapper/README.md @@ -150,7 +150,7 @@ Here is the list of supported options: If using a block device for device mapper storage, ideally lvm2 would be used to create/manage the thin-pool volume that is then handed to docker to exclusively create/manage the thin and thin - snapshot volumes needed for it's containers. Managing the thin-pool + snapshot volumes needed for its containers. Managing the thin-pool outside of docker makes for the most feature-rich method of having docker utilize device mapper thin provisioning as the backing storage for docker's containers. lvm2-based thin-pool management