The device mapper graphdriver uses the device mapper thin provisioning module (dm-thinp) to implement CoW snapshots. For each devicemapper graph location (typically /var/lib/docker/devicemapper
, $graph below) a thin pool is created based on two block devices, one for data and one for metadata. By default these block devices are created automatically by using loopback mounts of automatically created sparse files.
The default loopback files used are $graph/devicemapper/data
and $graph/devicemapper/metadata
. Additional metadata required to map from docker entities to the corresponding devicemapper volumes is stored in the $graph/devicemapper/json
file (encoded as Json).
In order to support multiple devicemapper graphs on a system, the thin pool will be named something like: docker-0:33-19478248-pool
, where the 0:33
part is the minor/major device nr and 19478248
is the inode number of the $graph directory.
On the thin pool, docker automatically creates a base thin device, called something like docker-0:33-19478248-base
of a fixed size. This is automatically formatted with an empty filesystem on creation. This device is the base of all docker images and containers. All base images are snapshots of this device and those images are then in turn used as snapshots for other images and eventually containers.
docker info
As of docker-1.4.1, docker info
when using the devicemapper
storage driver will display something like:
$ sudo docker info [...] Storage Driver: devicemapper Pool Name: docker-253:1-17538953-pool Pool Blocksize: 65.54 kB Data file: /dev/loop4 Metadata file: /dev/loop4 Data Space Used: 2.536 GB Data Space Total: 107.4 GB Data Space Available: 104.8 GB Metadata Space Used: 7.93 MB Metadata Space Total: 2.147 GB Metadata Space Available: 2.14 GB Udev Sync Supported: true Data loop file: /home/docker/devicemapper/devicemapper/data Metadata loop file: /home/docker/devicemapper/devicemapper/metadata Library Version: 1.02.82-git (2013-10-04) [...]
Each item in the indented section under Storage Driver: devicemapper
are status information about the driver.
Pool Name
name of the devicemapper pool for this driver.Pool Blocksize
tells the blocksize the thin pool was initialized with. This only changes on creation.Data file
blockdevice file used for the devicemapper dataMetadata file
blockdevice file used for the devicemapper metadataData Space Used
tells how much of Data file
is currently usedData Space Total
tells max size the Data file
Data Space Available
tells how much free space there is in the Data file
. If you are using a loop device this will report the actual space available to the loop device on the underlying filesystem.Metadata Space Used
tells how much of Metadata file
is currently usedMetadata Space Total
tells max size the Metadata file
Metadata Space Available
tells how much free space there is in the Metadata file
. If you are using a loop device this will report the actual space available to the loop device on the underlying filesystem.Udev Sync Supported
tells whether devicemapper is able to sync with Udev. Should be true
.Data loop file
file attached to Data file
, if loopback device is usedMetadata loop file
file attached to Metadata file
, if loopback device is usedLibrary Version
from the libdevmapper usedThe devicemapper backend supports some options that you can specify when starting the docker daemon using the --storage-opt
flags. This uses the dm
prefix and would be used something like docker -d --storage-opt dm.foo=bar
.
These options are currently documented both in the man page and in [the online documentation](https://docs.docker.com/reference/commandline/daemon/#docker- execdriver-option). If you add an options, update both the man
page and the documentation.