#I have a question regarding buildkit and

1 messages · Page 1 of 1 (latest)

late loom
#

I mean you can set up two separate nodes running buildkit, one for each platform, and then as the client distribute builds as needed. If you setup the right remote caching configuration you might be able to get them to share cache (for non-platform specific layers they could have in common, such as layers created with FileOp)

#

But most of the work there is on you as the client, buildkit is only single-node today as far as each buildkitd instance is concerned

#

An individual buildkitd knows how to use qemu to build multiple arches, but obviously that has performance costs relative to what you're describing

#

And also buildkitd's architecture is very much setup to support multi-node workers in the future. It will still take significant effort to add that feature, but not "rewrite everything" effort

honest nexus
#

Note that buildkit is linux-only. So we can get linux-arm nodes but not mac workers

#

in other words: multi-arch hard but doable. full multi-platform much harder