5 minutes ago, Squid said:

No.

 

You can get the container sizes right from the docker tab (Container Size button) to see which app is taking up which space (not quite 100% accurate, but will give a good idea)

legit never saw that button. turns out its my instance of unmaniac running. not sure what is the cause. I have logs limited and mapping done correctly. Ill post on that thread to see if its a known issue.

 

Thank you sir/Ma'am

On 6/20/2021 at 10:49 AM, Aerodb said:

mapping done correctly

It's not just a question of the mappings. The settings within the application must only use paths that correspond to container paths in the mappings, case-sensitive.

On 6/21/2021 at 1:57 PM, trurl said:

It's not just a question of the mappings. The settings within the application must only use paths that correspond to container paths in the mappings, case-sensitive.

so if youre advising the mapping being case accurate, yes i have confirmed that is done. it seems that the docker author has mentioned that i have done something wrong with my mapping to the cache. still trying to determine what he means. im not encoding to ram since i only have 32gb and use most of that for plex transcoding. 

Sorry for warming up this again, but i think i need some help to find out what is writing in my docker.img.
at the moment im haveing 14 Docker Containers and my docker.img is used by 4,67GB.

But i cant find any information on whats writing to there...
I checked all mounts and can confirm that everything is mounted correctly.
Is there a way to check from inside the Container whats gets written somewhere else?

for example my nginxproxymanager is using 188MB inside the docker.img.
Running df inside the container shows me that the only thing that is located in the docker.img is /etc/resolv.conf, hostname and hosts.
So i guess the 188MB is the Container image it self is that correct?
Also is there a better way for checking what an container writes in the image?