Buildx should write a warning when builder disk space is low
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4.5k
- Forks
- 682
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 29
Description
When builder disk space is low, then builds can fail because of a lack of disk space - this can be incredibly frustrating to debug, because programs can fail to correctly propagate the out of disk space error to the user 😢
We can provide a better user experience in this case by warning the user before the build that the builder is running low on disk space to prompt the user to resolve this. Alternatively, we could print this warning only if the build fails, to reduce log spam.
We have all this information already through the client.DiskUsage call - we would just need to connect that call to the build functions.
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
No file or test is named. Locate the build entry points and the existing client.DiskUsage call, then trace how disk information can reach the build flow. Done means a low-space condition produces a clear user-facing warning, with the timing and threshold resolved and covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100