OMV drive keeps filling up

  • Hi Everyone,


    This forum and community have always been really helpful, so thanks so much for the help to date.


    Here's my current problem: My BananaPi OMV drive keeps filling up. Other posts have said that this has to do with improperly configured docker containers and that may be the case. I'm hoping someone could steer me in the right direction:


    root@bananapipro:~# df -h

    Filesystem Size Used Avail Use% Mounted on

    udev 445M 0 445M 0% /dev

    tmpfs 100M 14M 87M 14% /run

    /dev/mmcblk0p1 15G 14G 789M 95% /

    tmpfs 499M 0 499M 0% /dev/shm

    tmpfs 5.0M 4.0K 5.0M 1% /run/lock

    tmpfs 499M 0 499M 0% /sys/fs/cgroup

    tmpfs 499M 16K 499M 1% /tmp

    /dev/zram0 49M 3.0M 42M 7% /var/log

    folder2ram 499M 0 499M 0% /var/tmp

    folder2ram 499M 408K 499M 1% /var/lib/openmediavault/rrd

    folder2ram 499M 620K 498M 1% /var/spool

    folder2ram 499M 9.0M 490M 2% /var/lib/rrdcached

    folder2ram 499M 2.7M 496M 1% /var/log.hdd

    folder2ram 499M 4.0K 499M 1% /var/lib/monit

    /dev/sda1 917G 477G 440G 53% /srv/dev-disk-by-label-NAS

    folder2ram 499M 1.6M 497M 1% /var/cache/samba

    overlay 15G 14G 789M 95% /var/lib/docker/overlay2/1dbab0050e3577308 de8dd4e47457020771d45f622519607abbc6fb27d7282fb/merged

    overlay 15G 14G 789M 95% /var/lib/docker/overlay2/4cd4989533426e006 8f85f30f20ec871b2ef5029ddfc584a6c2f4b4f26fc3368/merged

    shm 64M 0 64M 0% /var/lib/docker/containers/db076d3b1b2b447 473a983d964fac6dcea41749fbeda2443c201fa9464d301b1/mounts/shm

    overlay 15G 14G 789M 95% /var/lib/docker/overlay2/80a8eceaeee9e0f33 bfc5a41466a0540918abeb1796013ff4d891ad5a1d071fa/merged

    shm 64M 0 64M 0% /var/lib/docker/containers/3d5c92a8ca43524 20bd235a7f631233fc5816a10c43924a2ce3bef5cc2658755/mounts/shm

    tmpfs 100M 0 100M 0% /run/user/0

    root@bananapipro:~#

  • Thanks! I'm running Transmission and Medusa. Any clue how to delete those files or modify how the containers store them?

    It just isn't possible to provide meaningful help when you haven't posted your current container configurations.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 5.x on ASRock Rack C2550D4I C0 Stepping - 16GB ECC - Silverstone DS380 + Silverstone DS380 DAS Box.

  • It would be better if you could take what is in that screenshot and convert it into a dicker run or dicker create command and post that. Wherever you got the docker image should have a sample file you can look at and correct to agree with your specific use case.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 5.x on ASRock Rack C2550D4I C0 Stepping - 16GB ECC - Silverstone DS380 + Silverstone DS380 DAS Box.

  • Okay thanks everyone for the help. I ended up having some time to mess with the system today and I discovered the following with the following command:


    root@bananapipro:/var# sudo du -sh /var/lib/docker/overlay2

    11G /var/lib/docker/overlay2


    When I give an 'ls' command in that folder just a bunch of numbers and letters fill the screen.


    So that's the folder that is filling up.


    Could anyone tell me what that folder holds, what can I delete and how to keep it from filling up in the future?

  • You need to move your docker folder from the default location at


    /var/lib/docker


    to


    /srv/dev-disk-by-<id of your storage disk> /docker


    Then you'd need to go into OMV-Extras->Docker->Docker Storage and enter the new path. If you want to save your old docker contents, you're going to need to ssh into your system and copy it to your storage drive using the bash shell, something like this


    Code
    $ sudo cp -Rf /var/lib/docker /srv/dev-disk-<id of your storage disk>/docker


    I just had the same problem, the above is what I did to fix it and it works fine.

  • Fantastic. Thanks for the help.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!