Docker device-mapper Storage Backend: Difference between revisions
Jump to navigation
Jump to search
(→Info) |
|||
Line 45: | Line 45: | ||
Base size is the maximum size that a container/image can grow to. | Base size is the maximum size that a container/image can grow to. | ||
Reported with [[docker info]] and also with [[docker inspect]]: | Reported with [[docker info]] and also with [[docker inspect]] {{.GraphDriver.Data.DeviceSize}}: | ||
... | ... |
Revision as of 17:57, 13 February 2018
External
- https://docs.docker.com/engine/userguide/storagedriver/device-mapper-driver/
- https://docs.docker.com/storage/storagedriver/device-mapper-driver/
Internal
Overview
Device-mapper driver metadata is stored in /var/lib/docker/devicemapper/metadata. Docker state can be reset by stopping docker and by removing /var/lib/docker/devicemapper/metadata directory. This will destroy existing docker images and containers and all the docker metadata.
Info
At runtime, general statistics on the devicemapper storage driver can be obtained with:
docker info Storage Driver: devicemapper Pool Name: docker_vg-container--thinpool Pool Blocksize: 524.3 kB Base Device Size: 10.74 GB Backing Filesystem: xfs Data file: Metadata file: Data Space Used: 16.81 GB Data Space Total: 53.57 GB Data Space Available: 36.76 GB Metadata Space Used: 3.338 MB Metadata Space Total: 54.53 MB Metadata Space Available: 51.19 MB Thin Pool Minimum Free Space: 5.357 GB Udev Sync Supported: true Deferred Removal Enabled: true Deferred Deletion Enabled: true Deferred Deleted Device Count: 0 Library Version: 1.02.140-RHEL7 (2017-05-03) ...
Base Device Size
Base size is the maximum size that a container/image can grow to.
Reported with docker info and also with docker inspect Template:.GraphDriver.Data.DeviceSize:
... "GraphDriver": { "Name": "devicemapper", "Data": { "DeviceId": "3315", "DeviceName": "docker-253:3-12968682-7827556d545926857d669f5f9bb7fd69083e7e98636ff3f060d352223f4918ab", "DeviceSize": "10737418240" } } ...
Set with
-dm.basesize=20G