Warning [serverName] - Docker image disk utilization of 81%

Docker utilization of image file /mnt/user/system/docker/docker.img

Hi there... I seem to have some issue where my docker, during use, fills up and I get these warning messages like the one above.... but then they go down a bit latter

Notice [serverName] - Docker image disk utilization returned to normal level

Docker utilization of image file /mnt/user/system/docker/docker.img

I am sure it is some issue with temporary files, but I need to find a way to work out wich of the many dockers is doing this...

TL:DR :

Is there a way, maybe with logs, I can find out which docker is eating all the space in the docker.img with it's temporary files?

Docker tab, "Container size" button on the bottom shows alot.

Writable column is the data the app has written into the image.

Misconfigured containers that download into docker.img itself will have that column rather large.

I don't know of any other way to see it. Try to catch it in the act before it moves content out from docker.img?

Edit:

For ARR stack, maby transcoding directory is not set outside, anything that downloads - download directory, etc...

Edited December 7, 2025Dec 7 by Lavoslav

I have nearly the same problem and I just checked the container sizes but I don´t know if any of those containers are unreasonably big. I am at 91% of the docker.img which is 35GB big.

What container should be smaller in size?

thanks

Can anybody help with this? Container, Writable and Log are slowly getting bigger. I am now standing at 31.8GB, 1.88GB and 2.72 GB. What can I do?

homeserver-diagnostics-20251226-1039.zip

2 hours ago, stainless_steve said:

Can anybody help with this? Container, Writable and Log are slowly getting bigger.

Totals aren't really helpful, you need to look at which container(s) increase.

I understand, and already identified the containers that are increasing in size. But I what I don´t understand if that is normal and if the container sizes are reasonable in size.

Is it possible to just delete all the logs of the containers somehow?