A build with BuildKit cannot be fully used as a library
Open
Nobody has claimed this yet.
kind/feature
status/0-triage
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Description
BuildKit build implementation uses standard streams instead of docker client instance ones:
- The user cannot work with output because it is written to standard output and error streams.
NOTE: this is a follow up issue since https://github.com/docker/cli/issues/2889 was closed but not completely fixed
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 at cli/command/image/build_buildkit.go and compare its stream handling with cli/command/cli.go#L51-L53, then review issue #2889 for prior context. Done means BuildKit output is routed through the Docker client instance streams so library users can consume it rather than receiving writes only on process standard output/error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli, developer-experience
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100