coreos / coreos/coreos-assembler
Consider pruning osbuild data from cache qcow2
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 393
- Forks
- 193
- Avg merge
- 17h 6m
- Merged PRs (30d)
- 5
Description
Once in a while, when building a disk image I hit ENOSPC on the cache qcow2 so then I have to delete it so it gets recreated. I think the issue here is that we never prune from there. But it would make sense to do so whenever we prune builds.
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 locating the build-pruning logic and the code that manages the cache qcow2, then determine how osbuild data is retained there. Done means pruning builds also removes obsolete osbuild data from the cache qcow2 so image builds are less likely to fail with ENOSPC.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100