Docker Image Utilization

[zbron]

Been driving myself a bit crazy trying to determine what is filling up my Docker.img - I've already increased the size of the image way more than I should have and am still struggling (91% of a 65GB image file). I've attached the results of the container size button on the docker tab, the results of running docker system df -v, and would much appreciate any help you could offer.

In my search to determine the culprit here, I ran this command du -ah /var/lib/docker/containers/ | grep -v "/$" | sort -rh | head -60 which resulted in the following

 

I then ran find /var/lib/docker/containers/ -type f -name "*.log" -delete which seems to have deleted the 45G files from the above picture, but the docker image utilization hasn't changed. I'm pretty desperate for help at this point.

 

Edit: literally the moment I was about to submit this topic, the docker image utilization went to <15%. So less urgent, but curious about the following.

• Was deleting the gigantic logs above the fix? How can I avoid these files growing so large in the future? Alternatively, any thoughts as to why this magically was fixed? The only other thing I did was turn off all my dockers (and turn them back on after utilization was under control)
• I gather my docker image file is WAY to big, and could be problematic. What should I do here in order to preserve all my dockers/settings as is?

Edited November 20, 2019 by zbron
Just mistyped something

[Squid]

Can you post the output of

php /usr/local/emhttp/plugins/dynamix.docker.manager/include/GetContainerSize.php

Errors should not be happening on that first screenshot..

Edited November 20, 2019 by Squid

[zbron]

Seems like the problem is not fixed as I had to go through the same process todaySee above for results for the php command

[zbron]

Forgot to be more specific in previous post, the exact same 45G file showed up in response to du -ah /var/lib/docker/containers/ | grep -v "/$" | sort -rh | head -60, so I followed up by using the same find /var/lib/docker/containers/ -type f -name "*.log" -delete that seemed to work (temporarily) yesterday. These two commands were run before I posted the output of the php command.

[Squid]

The errors listed in the popup are because you are manually deleting the logs.  You are better off though doing this

 

https://forums.unraid.net/topic/57181-real-docker-faq/#comment-564326

 

[zbron]

Thank you, I'll add that to all my containers and report back if it doesn't work. Is there any way to tell from what I posted which docker was creating the gigantic log?

 

Assuming this does work, what's the easiest way to shrink the docker.img file down to a more reasonable 35GB or so? Or is it not worth it?

Edited November 21, 2019 by zbron

[Squid]

Just now, zbron said:

shrink the docker.img

The way you shrink is Settings - Docker, stop the service, then delete the image, then set a new size and re-enable the service.   

 

Followed by Apps, Previous Apps, check off what you want and hit install.

[zbron]

Will this blow up everything/settings/etc.? Or will I simply need to make sure all dockers are configured the same way as before?

[Squid]

4 minutes ago, zbron said:

Will this blow up everything/settings/etc.?

No

4 minutes ago, zbron said:

Or will I simply need to make sure all dockers are configured the same way as before?

They will be, with no adjustments necessary

[zbron]

Thank you Squid, really appreciate the help.