Hi all,

I've read lots of other threads that cover this issue, and the best approach to identify the problem always seem ambiguous or different. I run Nextcloud, Plex, related arr's and thats about it. Started with a 20GB image, increased it to 30GB when it first filled up, and here I am again.

I've checked the mappings of all my containers and can't see any obvious errors. My Plex transcodes to RAM.

Can anyone advise on the best process of elimination for solving this problem?

 

themagiceye-diagnostics-20230510-2128.zip

Edited May 10, 20233 yr by nametaken_thisonetoo
Clarity

Start with checking container size with built in functionality on docker tab

 

If that's not sufficient, look at these scripts - https://github.com/SpaceinvaderOne/Unraid_check_docker_script

 

In the end, you need to find the container that is writing data without a volume mount and hence growing in size

Edited May 10, 20233 yr by apandey

The usual cause of filling docker.img is an application writing to a path that isn't mapped.

1 hour ago, nametaken_thisonetoo said:

checked the mappings of all my containers

You have to check more than just the mappings. Each path the application is writing to should be mapped to host storage. You need to pay attention to the paths configured within the application.

 

Linux is case-sensitive, so if the application is writing to "/downloads" and you have mapped "/Downloads" instead, these are different.

 

Also, relative paths (not beginning with / ) can't be mapped so if an application is writing to a relative path, it must be relative to a path that is mapped.