Garbage cleanup #23860
Replies: 6 comments 1 reply
-
I would not have a problem with these services being defined and not enabled by default. Perhaps with reference in the prune man pages. |
Beta Was this translation helpful? Give feedback.
-
Given that this kind of garbage cleanup isn't something that you would enable by default makes me think that not everyone would want it which makes me wonder what I am doing wrong to cause so much garbage to pile up. I am testing CI pipelines that use containers to do their work in, so repeatedly I run something along the lines of:
which depending on the churn of the But is there something I should be doing that would prevent the pile up? |
Beta Was this translation helpful? Give feedback.
-
These thing can never turned on by default. How do we know just because a container is stopped that it should be removed? There could be data in there were a user care about... In general shipping some systemd service + timer is fine but enabling that by default is not possible IMO as this will break many users one way or another. |
Beta Was this translation helpful? Give feedback.
-
Fair enough. But then how should a machine that is a CI/CD runner that starts containers over and over again all day long, (i.e. 24x7) be starting and/or managing containers such that they do no pile up creating such a big garbage pile that it needs to be pruned periodically, if there can also be containers that should not be pruned because they may contain wanted data? IOW, as it seems that pruning containers is a big hammer that can cause collateral damage, how should one be starting and/or managing containers so that they do not need to be pruned periodically? I.e how can I avoid the need to prune periodically? What am I doing wrong that is leaving so many containers around that they need to be pruned? |
Beta Was this translation helpful? Give feedback.
-
A friendly reminder that this issue had no activity for 30 days. |
Beta Was this translation helpful? Give feedback.
-
Are you running your containers with the |
Beta Was this translation helpful? Give feedback.
-
Feature request description
Podman fills up my
~
.Suggest potential solution
I wonder if it would be appropriate for the podman packaging to include periodic (i.e. cron or systemd timer) garbage cleaners to remove unused containers and images. I seem to regularly need to do:
It would be nice to have this preventative action happen without the need for every individual to have to re-create it.
Have you considered any alternatives?
Of course, each individual solving this problem for themselves, but why should every podman user have to venture down this path, re-inventing wheels?
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions