Device Mapper storage driver¶
MCR hosts that run the devicemapper
storage driver use the loop-lvm
configuration mode by default. This mode uses sparse files to build
the thin pool used by image and container snapshots and is designed to work
without any additional configuration.
Note
Mirantis recommends that you use direct-lvm
mode in production
environments in lieu of loop-lvm
mode. direct-lvm
mode is more
efficient in its use of system resources than loop-lvm
mode, and you can
scale it as necessary.
For information on how to configure direct-lvm
mode, refer to the Docker
documentation, Use the Device Mapper storage driver.