Skip to content

Provide a Github Action example of multiple runners pushing to multiple registries without bake #21580

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
1 task done
FoxxMD opened this issue Dec 6, 2024 · 1 comment · Fixed by #21664
Closed
1 task done
Assignees
Labels
area/build Relates to Dockerfiles or docker build command lifecycle/locked

Comments

@FoxxMD
Copy link

FoxxMD commented Dec 6, 2024

Is this a docs issue?

  • My issue is about the documentation content or website

Type of issue

I can't find what I'm looking for

Description

It's not uncommon to want to use Github Actions to push to build an image and push to multiple registries. The docker docs even have an example of this using build-push-action which is very straightforward. However this strategy uses QEMU for multi-platform which is slow.

There is already a docs example of building multi-platform image using multiple runners but the example only shows usage for pushing to one registry.

The bake example does show how to push to multiple registries but that requires modifying a user's entire build strategy to use bake instead of build.

Location

https://docs.docker.com/build/ci/github-actions/multi-platform/#distribute-build-across-multiple-runners

Suggestion

Please provide a modified version of the Distribute build across multiple runners example that shows how a user could push the built image to multiple registries.

Thanks

@FoxxMD FoxxMD added the status/triage Needs triage label Dec 6, 2024
@dvdksn dvdksn self-assigned this Dec 18, 2024
@dvdksn dvdksn added area/build Relates to Dockerfiles or docker build command and removed status/triage Needs triage labels Dec 18, 2024
@docker-robot
Copy link

docker-robot bot commented Jan 20, 2025

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

/lifecycle locked

@docker-robot docker-robot bot locked and limited conversation to collaborators Jan 20, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/build Relates to Dockerfiles or docker build command lifecycle/locked
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants