docker imgage file filling up

[dehein2]

Hi all,

 

i seem to have mis-configured containers as the docker img. file is filling up and is currently at 75% (16gb total). What i checked on the docker tab is the container size:

 

 

I guess that is not including data in the appdata directory correct? So It's only data stored in the actual container (which should be static and not include user data - correct?)

 

So lets take the first for example: openaudible

I guess 1.06gb is way to much as all the downloads are stored in the appdata folder mapped as /config. This is set in the preferences of the app and files "arrive" in the appdata folder.

 

so the question is: How can i dig deeper and see where the 2gb come from?

 

Thanks

 

 

 

[Squid]

7 minutes ago, dehein2 said:

so the question is: How can i dig deeper and see where the 2gb come from?

Overhead?  According to the screen shot, you're using ~15G of what is presumably a 20G docker image with nothing out of the ordinary - Nothing is "downloading" to the image, logs are normal etc.  There are some auxiliary files stored in the image (notably icons) along with the last backup log for CA Appdata Backup/Restore (This can potentially be huge depending upon the number of files within appdata)

 

ie: You're worrying too much about working out where the 2G is coming from.  The 75% warning (presumably you've been told about that via FCP) is hardcoded at that percentage, but I see nothing wrong.  You can always increase the size of the image if you want

[dehein2]

ok cool - i was just worried i have some kind of leak

[dehein2]

Thanks a lot