-
Notifications
You must be signed in to change notification settings - Fork 152
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
Feature request: append builder #115
Comments
@febus982 Sgtm. I think instead of a boolean parameter for |
Great idea. I would use that to append another remote "node" (i.e. an AWS graviton instance for example to build my ARM images) accesible via SSH, like:
So having options to do that in the |
I created an action out of it for our particular use-case (should also work for the kubernetes case). It also loads an SSH key before if we need that. https://github.com/marketplace/actions/append-buildx-nodes |
@baschny You saved my time. Thanks a lot. |
You can now append nodes to existing builder, see https://github.com/docker/setup-buildx-action/blob/master/docs/advanced/append-nodes.md for more info. |
There are certain scenarios where QEMU performance is simply terrible.
A much performant approach is to use multiple native buildx
buildersnodes.We can already do it using a bash script :
Would it be possible to introduce an
append
boolean parameter? Eventually it could be anappend_to
accepting a step id (or the builder instance name from the output)The text was updated successfully, but these errors were encountered: