May 11, 20251 yr I have a 100GB docker image disk right now. As I have added more containers, I have had to iteratively increase the image disk size. This is not a misconfiguration, containers are not being written to to contribute to the size. The size is mainly coming from the docker images themselves - I have multiple ML images with models etc which are 5-10GB each adding up quickly. While updating versions, having 2 copies gets docker image into high utilization warning zone I have been increasing the disk image size slowly, adding about 10-20GB in each iteration. Is there any downside if I gave it a large headroom and not worry about it for a while? In other words, is making it 200GB OK without any side effects? I keep an eye on growth and any write activity into containers separately, so I am less likely to not notice a misconfigured container that eats up space via writes into the container
May 11, 20251 yr Community Expert Solution why bother with it over and over again? Give it a directory on a pool device and it can grow and grow (until the device is full) without beeing pampered by you every few weeks.
May 11, 20251 yr Author 36 minutes ago, MAM59 said: why bother with it over and over again? Give it a directory on a pool device and it can grow and grow (until the device is full) without beeing pampered by you every few weeks. Indeed, I don't want to bother when I know where the space is going. I wasn't aware that I can use a directory instead of a disk image. Will certainly help and be simpler. Will look to switch to this and report back. Thanks a lot for the pointer
May 11, 20251 yr Author 1 hour ago, apandey said: Will look to switch to this and report back Seems this involves re-installing the templates from previous apps. I was on a journey switching my containers to docker-compose, so I would first finish that migration before switching over. that way, all my state can roll out from a git repo via ansible
May 11, 20251 yr Community Expert Another trick would be to install the plugin "appdata backup" and run it it creates backups from your docker settings. You can then switch and use the plugin again to restore previous settings stresslessly 🙂
May 11, 20251 yr Author 31 minutes ago, MAM59 said: Another trick would be to install the plugin "appdata backup" and run it it creates backups from your docker settings. You can then switch and use the plugin again to restore previous settings stresslessly yes, been there and done that. Unfortunately, it's a black box and I am more comfortable with gitops approach for config management where I know what is applied and can debug / change it of its not to my liking. Also, it unifies install / update and restore all to a single process, so I don't have to rethink when it comes to such infrequent maintenance. Personal preferences I guess I do have appdata backup runiing to take nightly backups along with all my data. But thats more of a fallback for operational errors rather than for data backups
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.