Make frontend aware of any output tags assigned to the build
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.3k
- Forks
- 1.5k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 48
Description
Overview
Some image build processes (like Cloud Native Buildpacks) rely on intelligently reusing layers from the images built previously. Unfortunately, it doesn't seem like BuildKit provides a way to get the information on what reference(s) the output image will be tagged as. As a result, implementing something like this would mean that users have to duplicate the definition, for instance:
... build -t myappimage --build-arg TAG=myappimage .
Would it be possible for the frontend to somehow be aware of the output tag(s)?
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
The issue names no files, tests, or entry points. Start by tracing how BuildKit frontends receive build options and how output image references are represented. Done would require an agreed mechanism for frontends to access output tags, along with tests documenting the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100