Warning message for lvm devmapper running on top of loopback devices

Signed-off-by: Shishir Mahajan <shishir.mahajan@redhat.com>
This commit is contained in:
Shishir Mahajan 2015-08-04 14:33:00 -04:00 committed by Tibor Vass
parent 8387eacede
commit d5394a0d5f
1 changed files with 6 additions and 0 deletions

View File

@ -192,6 +192,12 @@ options for `zfs` start with `zfs`.
resize support, dynamically changing thin-pool features, automatic thinp resize support, dynamically changing thin-pool features, automatic thinp
metadata checking when lvm activates the thin-pool, etc. metadata checking when lvm activates the thin-pool, etc.
As a fallback if no thin pool is provided, loopback files will be
created. Loopback is very slow, but can be used without any
pre-configuration of storage. It is strongly recommended that you do
not use loopback in production. Ensure your Docker daemon has a
`--storage-opt dm.thinpooldev` argument provided.
Example use: Example use:
docker daemon --storage-opt dm.thinpooldev=/dev/mapper/thin-pool docker daemon --storage-opt dm.thinpooldev=/dev/mapper/thin-pool