Replies: 1 comment 1 reply
-
We don't have any load balancing pattern with nodes, they are only used to match the target platform you want to build on. So even if you have 5 nodes supporting
And thanks for using |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We recently started migrating our container image build process to use
buildx bake
. So far it has been working great, with only minor issues. In our setup there is a single "bake" invocation, which eventually results in hundreds (slightly different) container images.We wanted to speed up the build process and were wondering if there is a way to configure buildx so that it does not always pick the first node that satisfies some platform requirements. It seems that currently if we want to build for
linux/amd64
, it will always pick the first node in the configuration (we are using aremote
driver with multiple nodes exposing buildkit via TCP).I understand that this is needed in some cases when targets share some build stage, but in our case we have completely different targets defined in our bake file. Is there a way to achieve this? If not, would this be a feature that would be considered for inclusion? If so, I could start working on it.
Beta Was this translation helpful? Give feedback.
All reactions