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
As pointed out by Anthony Sottile on Twitter, probably the easiest way to get around this is to build separate images in CI (using GitHub Actions for linux/amd64 and Cirrus CI for linux/arm64) with something like
on Cirrus CI (aarch64). Once both of those images are up on the container registry of choice (here Docker Hub but probably also want to do this for ghcr as well later) would then want to in another workflow do
I assume that as docker manifest create --help doesn't make it clear, there is no way to to multiple manifest tags at once and so to also do a tag of matthewfeickert/pythia-python:pythia8.308 it would require
I'm also not sure if I'll need to manually use docker manifest annotate to add in platform architecture and os information, or if that will get automatically picked up from use of the --platform tag in the docker buildx build step.
I already know how to do this manually with things like
but to do this in CI this is too slow (takes almost 6 hours) with
taking far too long and can time out.
As pointed out by Anthony Sottile on Twitter, probably the easiest way to get around this is to build separate images in CI (using GitHub Actions for
linux/amd64
and Cirrus CI forlinux/arm64
) with something likeon GitHub Actions (
x86_64
) andon Cirrus CI (
aarch64
). Once both of those images are up on the container registry of choice (here Docker Hub but probably also want to do this forghcr
as well later) would then want to in another workflow doI assume that as
docker manifest create --help
doesn't make it clear, there is no way to to multiple manifest tags at once and so to also do a tag ofmatthewfeickert/pythia-python:pythia8.308
it would requireThe text was updated successfully, but these errors were encountered: