WARNING: the devicemapper storage-driver is deprecated, and will be removed in a future release.
WARNING: devicemapper: usage of loopback devices is strongly discouraged for production use.
Use `--storage-opt dm.thinpooldev` to specify a custom block storage device.
Docker docs provides the solution, namely, to configure direct-lvm mode for production.
To close this ticket:
read all the instructions at docker docs for understanding
identify large(ish) volumes on dev-ctmd, stage-ctmd, heal-ctmd, and ctmd
execute all the commands on dev-ctmd, taking care to document all the switches, and the order, and test.
alert Dawn/Duke and execute again on stage-ctmd and test
alert Dawn/Duke and execute again on heal-ctmd, ctmd
df
on ctmd.renci.org shows /var at 68% usage, anddu -sh /var/lib/docker/devicemapper
yields 34G, very high for this application.This stackoverflow thread sheds some light on the issue.
Finally,
docker info
uncovers the problem:Docker docs provides the solution, namely, to configure direct-lvm mode for production.
To close this ticket: