Docker overlayfs filling up 80GB disk

    • OMV 4.x (stable)

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Docker overlayfs filling up 80GB disk

      Filesystem Size Used Avail Use% Mounted on
      udev 5.9G 0 5.9G 0% /dev
      tmpfs 1.2G 9.2M 1.2G 1% /run
      /dev/sda1 76G 71G 1.2G 99% /
      tmpfs 5.9G 0 5.9G 0% /dev/shm
      tmpfs 5.0M 0 5.0M 0% /run/lock
      tmpfs 5.9G 0 5.9G 0% /sys/fs/cgroup
      RAID-Z1_SkyPool1 15T 1.5T 13T 11% /SkyPool1
      tmpfs 5.9G 0 5.9G 0% /tmp
      overlay 76G 71G 1.2G 99% /var/lib/docker/overlay2/e718b1b50396ec605db739db336454a2c22c329dd8d9986b2cdc0012d1ceb209/merged
      shm 64M 0 64M 0% /var/lib/docker/containers/a68aa45cc45f1a5578caeb9e83f0e2d43d5d6b018d3f1de90d49bfd7f0971e44/shm



      df shows overlayfs is using a ridiculously huge amount of space (71 GB). The only containers active are plex, sonarr, radarr, and transmission. Interestingly, vmware shows the vmdk is only 21 GB so I don't understand what is going on. Any ideas on what might be causing this behavior?

      I can go back to a snapshot or mount a backup of my vmdk but I don't want to configure docker containers again only to have the same situation occur.
      Fractal Design Node 304:
      VMWare vSphere 6.5 | OMV4.x on Debian 9 (Stretch): Asrock H270M-ITX - i3-7100 - 16GB DDR4 - 1x 80GB vmdk on Samsung 960 EVO 250GB PCIe NVMe SSD (system drive) - 1x 120GB vmdk on Toshiba 450GB HHD (docker data) - 3x Seagate IronWolf 8TB HDD (RDM physical passthrough, RAID-Z1 Pool)
    • Is normal, leftover volumes sometimes, others is the logfile of the container stdout writing to the disk, dangling images.
      You can run a cleanup with

      docker system prune

      For volumes is
      docker volumes prune

      There is no info on how to see if the log file has reach a massive size. But docker inspect containername can tell you where the file is located and check it for your self.
      New wiki
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server
    • Thanks for the reply. I moved all docker data to a different virtual disk. So far I haven't had any more issues.
      Fractal Design Node 304:
      VMWare vSphere 6.5 | OMV4.x on Debian 9 (Stretch): Asrock H270M-ITX - i3-7100 - 16GB DDR4 - 1x 80GB vmdk on Samsung 960 EVO 250GB PCIe NVMe SSD (system drive) - 1x 120GB vmdk on Toshiba 450GB HHD (docker data) - 3x Seagate IronWolf 8TB HDD (RDM physical passthrough, RAID-Z1 Pool)