`prune`: filtering out `ADD --checksum=... https://...` entries
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4.5k
- Forks
- 682
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 29
Description
Description
I'd like to be able to run docker buildx prune but keep in cache the pinned ADD downloads.
Could we extend on the --filter=.. syntax?
Side curiosity: why are these cache entries marked Mutable: true?
From my understanding of du's docs that'd mean that its size can grow.
Is there a missed optimization opportunity of in the ADD op here, setting mutable=false?
cc https://github.com/moby/buildkit/issues/975#issuecomment-490586307
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 with the docker buildx prune filter handling and the referenced docs/reference/buildx_du.md description of mutable cache entries; use the linked BuildKit discussion for context on ADD --checksum behavior. Done should define and verify a filter that preserves pinned HTTPS ADD downloads, while separately determining whether the mutable status is in scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, dockerfile, go
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100