System Drive full because of Overlay

  • I can't log in any more on the webinterface of my OMV.
    I find that my systemdrive is full.
    but i am wondering why so I check with df -h whats going on
    df -h
    Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf
    udev 7,8G 0 7,8G 0% /dev
    tmpfs 1,6G 15M 1,6G 1% /run
    /dev/nvme0n1p1 102G 101G 0 100% /
    tmpfs 7,8G 0 7,8G 0% /dev/shm
    tmpfs 5,0M 0 5,0M 0% /run/lock
    tmpfs 7,8G 0 7,8G 0% /sys/fs/cgroup
    tmpfs 7,8G 4,0K 7,8G 1% /tmp
    /dev/md0 5,5T 3,0T 2,5T 55% /srv/dev-disk-by-label-Data
    overlay 102G 101G 0 100% /var/lib/docker/overlay2/22ff32952e87db69bd993db6e6134bfabd66895428f38eb41fad4d4f2c257fa9/merged
    overlay 102G 101G 0 100% /var/lib/docker/overlay2/7d82c451fae7cb15e4300f1f8345010fa31e845bc902bbba971f786a2e3f3e2e/merged
    overlay 102G 101G 0 100% /var/lib/docker/overlay2/68466f0c151d6bcd796b1ad89bedeeb93ca6760cbcceafd58ae108624ebf9ddd/merged
    shm 64M 0 64M 0% /var/lib/docker/containers/be4d5856a4f643edcea349dfac631c90f77332ee9a04f40d1f810090e65a5aef/mounts/shm
    shm 64M 0 64M 0% /var/lib/docker/containers/506ccad68027a5914f082ebd10ce0571f2b619137563464c8a3e177a4ca1377f/mounts/shm
    shm 64M 0 64M 0% /var/lib/docker/containers/cef665f2e43eeefb49b16683a219336def32eefdfe23914456bb2e31ac32351a/mounts/shm
    overlay 102G 101G 0 100% /var/lib/docker/overlay2/ff43d4d45067e3c9a87d845d87659d55e0355a276c3afaf67ab77039512cfe38/merged
    shm 64M 4,0K 64M 1% /var/lib/docker/containers/485e4b9cd0012fb25c46fedd8dc5d222039c752f4173f95742366a710fb8bbec/mounts/shm


    what is these overlay? iam sure that i mount the data drive of the docker containers on my data raid and not on my systemdrive. How i can fix this without an fresh installation? ;(

    • Offizieller Beitrag

    helps for me, but how i can prefend this problem?

    Depends on what you are running in Docker, you could install Watchtower and add --cleanup to the Command option, but Watchtower is not recommended if you are using Pi-Hole in Docker.

    • Offizieller Beitrag

    Depends on what you are running in Docker, you could install Watchtower and add --cleanup to the Command option, but Watchtower is not recommended if you are using Pi-Hole in Docker.


    Curious... I've seen you say this a couple of times. I don't use Pi-Hole so I'm clueless as to it's use.. but what's the issue with Watchtower? If you're running Watchtower to maintain other containers (Transmission, Calibre, etc..) is there a way to tell Watchtower to update everything but Pi-Hole? (I've never tried to exclude a container from updating).

    • Offizieller Beitrag

    Curious... I've seen you say this a couple of times. I don't use Pi-Hole so I'm clueless as to it's use.. but what's the issue with Watchtower?

    Watchtower itself is fine, but there was a thread on here with someone having issues with an update to Pi-Hole, the OP was using Watchtower, but because of the way Pi-Hole behaves having do an update via Watchtower appeared to corrupt Pi-Hole in some way. The consensus in respect of Pi-Hole was to delete it, including the networking and start again, I was having a discussion with @flmaxey on how this could be overcome and with some research there may be an answer, I'll try and find it.


    I have since moved Pi-Hole to DietPi on Rasp Pi, but even that has not been without it's problems until the recent DietPi update, now you can run pihole -up and it will update, instead of jumping through hoops.

    • Offizieller Beitrag

    Ok found it, to disable an update on a container:
    --label-enable --label=com.centurylinklabs.watchtower.enable=false pi-hole (i.e. pi-hole would be depend on how the user had specified the name)


    Does the above work, according to what I have found on github yes it does, it would have to be added to the 'Command' section in watchtower's Docker set up.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!