docker / docker/build-push-action
No imageid with docker/setup-buildx-action@v3
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.4k
- Forks
- 735
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 14
Description
Contributing guidelines
- I've read the contributing guidelines and wholeheartedly agree
I've found a bug, and:
- The documentation does not mention anything about my problem
- There are no open or closed issues that are related to my problem
Description
I felt like the default use was like in the readme to use
name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3
And in the readme it says that outputs include imageid. It took me a long time to figure out that doesn't happen if you use buildx. Maybe that should be made more clear in the readme? Or maybe other people knew to expect that?
Thanks!
Expected behaviour
Readme more specific
Actual behaviour
Imageid not in output with buildx
Repository URL
No response
Workflow run URL
No response
YAML workflow
n/a
Workflow logs
No response
BuildKit logs
No response
Additional info
No response
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 repository README section that lists outputs and the setup-buildx-action@v3 example. Verify how imageid is presented for the default Buildx usage, then update the README so its availability or limitation is explicit and confirm the documented behavior is accurate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, typescript
- Domain
- ci-cd, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100