You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 5, 2021. It is now read-only.
I had a question. I'd like to end up with the result that buildx provides -- one new tag with multiple images. However, my build takes a long time, especially when using qemu to emulate arm architectures. I'm currently running on GitLab CI (though I'm not 100% locked into that). The limit there is 3 hours, and when using a simultaneous build with buildx, the time goes over and the job fails. I split the task into multiple simultaneous jobs (one making amd64, one arm via qemu, and another arm64 vis qemu). This works fine, and things are recombined into one at the end with manifest. However, this makes four tags for what could just be one.
Is there any way you know of to have only one tag / manifest, while still building on separate machines?
Thanks!
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello!
I had a question. I'd like to end up with the result that
buildx
provides -- one new tag with multiple images. However, my build takes a long time, especially when using qemu to emulate arm architectures. I'm currently running on GitLab CI (though I'm not 100% locked into that). The limit there is 3 hours, and when using a simultaneous build with buildx, the time goes over and the job fails. I split the task into multiple simultaneous jobs (one making amd64, one arm via qemu, and another arm64 vis qemu). This works fine, and things are recombined into one at the end withmanifest
. However, this makes four tags for what could just be one.Is there any way you know of to have only one tag / manifest, while still building on separate machines?
Thanks!
The text was updated successfully, but these errors were encountered: