From 727c96be6130f320ce39d0611fcf96e6a24e58a1 Mon Sep 17 00:00:00 2001 From: Christy Perez Date: Wed, 26 Oct 2016 15:50:45 -0500 Subject: [PATCH] Fix thinpool name in storage opts flag The thinpool created in the example didn't have -tpool in the name, so if you copy these verbatim this fails. Signed-off-by: Christy Perez --- engine/userguide/storagedriver/device-mapper-driver.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/engine/userguide/storagedriver/device-mapper-driver.md b/engine/userguide/storagedriver/device-mapper-driver.md index b1aa1e1cf5..345da65e59 100644 --- a/engine/userguide/storagedriver/device-mapper-driver.md +++ b/engine/userguide/storagedriver/device-mapper-driver.md @@ -322,7 +322,7 @@ assumes that the Docker daemon is in the `stopped` state. Now that your storage is configured, configure the Docker daemon to use it. There are two ways to do this. You can set options on the command line if you start the daemon there: ```bash - --storage-driver=devicemapper --storage-opt=dm.thinpooldev=/dev/mapper/docker-thinpool-tpool --storage-opt=dm.use_deferred_removal=true --storage-opt=dm.use_deferred_deletion=true + --storage-driver=devicemapper --storage-opt=dm.thinpooldev=/dev/mapper/docker-thinpool --storage-opt=dm.use_deferred_removal=true --storage-opt=dm.use_deferred_deletion=true ``` You can also set them for startup in the `daemon.json` configuration, for example: