Disk usage is increasing with Docker containers about db1000n

[arriven]

I don't think this is something I can fix on my end. This is just the way docker works (it keeps all the older versions of images even if you don't use those). You can clean the system up by using docker system prune periodically which should remove unused data. Depending on your setup you can opt into running that command periodically with some cron or run it on every deploy but usually running that once in a while is enough

I'm also working on a side project that will allow using single image to run and auto-update db1000n in different environments (including containers) but it's not ready yet

[arriven]

As for updates: docker tracks the container lifetime by existance of the process with PID 1. Any kind of version update requires to restart the process in order to update the code and the new process won't get the same id as old one. In order to get around that you need to use some external process as the controller and that's what I'm planning to do

[MetaMmodern]

in different environments

@arriven what do you mean by this? Sounds cool, however AFAIK it's already possible to update db1000n without killing the container.

Forgot to say: thank you for the hint with prune)
But maybe there is a way to minimize the layer sizes that changes on every code update. I will try to investigate it in a week or two.

[arriven]

AFAIR, the only layer that changes between versions is the one where the executable resides and I doubt it'll be possible to cache that

[MetaMmodern]

Okay, I'll close this for how then. Thank you