docker system prune of exited containers
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Hi,
This is more of a feature request.
We are using docker system prune -a -f --filter "until=168h" in a daily cron job.
However if the container was created e.g. 2 weeks ago and is stopped at the time for this command to run, it will mean it gets deleted.
It would be great to have additional command like system prune container -a -f --filter "exited=168h" to remove containers exited 1 week ago.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Docker CLI implementation of docker system prune and its existing until=168h filter. Determine how an exited=168h container filter would fit the proposed command, and consider the work complete when stopped containers are retained or removed according to exit age rather than creation age.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100