Add support for min-free-space and max-used-space in build pruning
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 13d 8h
- Merged PRs (30d)
- 2
Description
Currently, API v1.48 supports min-free-space and max-used-space but docker-py doesn't handle that so, it would be beneficial to add their handling
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 docker-py’s build-prune handling and compare its supported options with the Docker Engine API v1.48 BuildPrune documentation. The work is done when min-free-space and max-used-space are handled and covered by the relevant existing tests, though the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100