docker / docker/github-builder
Bake build limited to single target
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 83
- Forks
- 23
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 8
Description
We currently limit Bake build to a single target: https://github.com/docker/github-builder-experimental/blob/e875129c872af249a9411fc0b1b1d1fe79ee6ddf/.github/workflows/bake.yml#L226-L228
Mainly because we don't have a way to discern which generated tags are associated to a target but also because a target could output build result locally while another one would push to registry.
We should document this but also explain how users can use a matrix strategy to solve this issue. For example using our matrix subaction: https://github.com/docker/bake-action/tree/master/subaction/matrix
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 linked .github/workflows/bake.yml lines 226-228 to understand the single-target limitation, then review the linked bake-action subaction/matrix example. Document why Bake is limited to one target and explain how users can use a matrix strategy to handle multiple targets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100