From 3497960ec5aab6dba91aef4ae2c455de2e1811ab Mon Sep 17 00:00:00 2001 From: Johanan Lieberman Date: Wed, 17 Aug 2016 21:46:33 +0300 Subject: [PATCH] Update device-mapper-driver.md Signed-off-by: Johanan Lieberman Upstream-commit: 086542a687235b0c3c8a6985755b918e2e93fcbc Component: engine --- .../engine/docs/userguide/storagedriver/device-mapper-driver.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/components/engine/docs/userguide/storagedriver/device-mapper-driver.md b/components/engine/docs/userguide/storagedriver/device-mapper-driver.md index a76417f74e..ef445023ca 100644 --- a/components/engine/docs/userguide/storagedriver/device-mapper-driver.md +++ b/components/engine/docs/userguide/storagedriver/device-mapper-driver.md @@ -210,7 +210,7 @@ you how to configure a Docker host to use the `devicemapper` storage driver in a `direct-lvm` configuration. > **Caution:** If you have already run the Docker daemon on your Docker host -> and have images you want to keep, `push` them Docker Hub or your private +> and have images you want to keep, `push` them to Docker Hub or your private > Docker Trusted Registry before attempting this procedure. The procedure below will create a logical volume configured as a thin pool to