What the subject says.
This has always left me puzzled. Why does gitlab-runner, something that only uses Docker, and is NOT part of the Docker install, apparently run a docker prune command?
As in, during an apt-get dist-upgrade, you get this message:
Check and remove all unused containers (both dangling and unreferenced) including volumes.
and promptly get to wait a long time for Docker to clean up a bunch of stuff.
Today I was running updates on my home server that’s been having some odd slow downs related to Docker. My update is currently stuck at 71%, and I think it’s been stuck there for the past 2 to 3 hours waiting on the prune command gitlab-runner triggered.
This has been behavior I’ve seen for years now. I’ve occasionally searched to see if anyone has brought it up, but have yet to find anything. I didn’t find anything when I looked today.
My opinion is that it is not appropriate for any program to run a prune command unless I tell it to, or installed it and expect that to be run as part of the process. I honestly cannot think of a good reason for gitlab-runner to do this.
But, before I go post a bug report, I thought I’d better see if anyone can share a different perspective, or point me at something explaining why. Maybe someone has better search skills that I do on this topic.
Anyone have any insight?
Thanks!