DragDom

Also When I stop running the backup plan the /tmp size shrinks to nothing. I can not seem to figure out how to stop this from happening.

To me it looks like the backup is writing data in /tmp I am assume it is a log of what the backup is doing.

Here is what I get after running the commands. 33G is in the directory / /tmp # add-pkg coreutils fetch http://dl-cdn.alpinelinux.org/alpine/v3.9/main/x86_64/APKINDEX.tar.gz fetch http://dl-cdn.alpinelinux.org/alpine/v3.9/community/x86_64/APKINDEX.tar.gz (1/3) Installing libattr (2.4.47-r7) (2/3) Installing libacl (2.2.52-r5) (3/3) Installing coreutils (8.30-r0) Executing busybox-1.29.3-r10.trigger Executing glibc-ldconfig-trigger-1.0-r0.trigger OK: 75 MiB in 123 packages /tmp # du -h -d1 --exclude /storage --exclude /proc --exclude /sys / 6.4M /bin 0 /dev 2.5M /etc 0 /home 5.7M /lib 0 /media 0 /mnt 139M /opt 4.0K /root 292K /run 592K /sbin 0 /srv 33G /tmp 80M /usr 36K /var 4.0K /lib64 84K /libexec 36K /defaults 68M /config 33G / /tmp #

This is the video that I followed. He never mentions anything about the docker.img. Just the access to the shares and that is it.

While running a backup My docker.img becomes 80% up to 99% full. It is 40GB. I did not change any of the default settings. Does anyone have any thoughts on why it is filling up. As soon as I stop the backup it clears up. Not sure what is causing this. Any help is appreciated.

I am brand new to using Unraid and dockers. I followed a guide on setting up Cloudberry to backup to Backblaze B2. When I am running a backup my Docker image will fill up and hit 85% or higher. Then when I stop the backup it drops back down. My docker.img is 40GB in size. It is on the array. I have looked at the docker FAQ and many posts say to not have it write to the img. I am struggle on how to not have cloudberry write to the docker.img. Any help is greatly appreciated! Cloudberry settings Docker settings After running docker ps -s