stridemat

Any ideas why this image would be taking nearly 3GB of Docker space? More than other data hungry containers such as Immich. All paths look to be configured correctly. I ask as I am currently using quite a lot of my allocated docker image and when updates are applied I get warning notifications: devid 1 size 30.00GiB used 27.64GiB path /dev/loop2

I have been having this issue as well. Any sign of a fix? I believe the backups are still fine, but every week I just get an error notification:

I still use it and like the added piece of mind with only a little inconvenience.

Thanks. I found it earlier and on a test all seems to be working.

Thanks. I am using usenet so will have to see if I can find this setting in SAB.

Hi, so I’m trying to get it so new media stays on the cache drive (media share) for a period of time, say 7 days in this example, but all other data in other shares moves from cache to array once a night - normal mover behaviour. I’m trying to avoid spinning up disks for recently added media that gets watched a few times. I have used the following settings. Will this work as desired?

That worked. Thank you.

Container is still working great (apart from the icon), but I was hoping it wasn’t the first sign of the container no longer being supported moving forward. Thanks for you work

Is this container still being supported?

Looks like the fix will be in the final build (it seems to be in rc7). Seems like a support headache though?

Looks like I'm waiting until a .1 or .2 release then

Im having the same. Any ideas?

Agreed. Much better than running in docker from a resilience point of view.

Is there likely to be a fix in the short term with this or is it a more fundamental change?

This fixed it for me!