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
tagging the system-test repo will trigger a new docker image of system-test to be built from that tag against versions defined in .github/workflows/Dockerfile.yml, the image will only be built for linux/amd64 cpu platform, therefore, clients that are on a am64 cpu platform, cannot run this image reliably, it will either fail or take extremely long for tests to finish due to docker emulation on host between cpu archs.
What would you like to see?
when you tag system-test repo, it will build and push a multi-platform docker manifest that has both a linux/amd64 and linux/arm64 version within, refer to quickstart for examples of how it accomplishes building same multi-platform manifests.
What alternatives are there?
manually build the arm64 on an arm64 host like a mac m1, then push that image manually to same repo.
The text was updated successfully, but these errors were encountered:
sreuland
changed the title
System Test: multiplatform docker image builds for tagged publish
System Test: multi-platform docker image builds for tagged publish
Sep 27, 2023
What problem does your feature solve?
tagging the system-test repo will trigger a new docker image of system-test to be built from that tag against versions defined in
.github/workflows/Dockerfile.yml
, the image will only be built forlinux/amd64
cpu platform, therefore, clients that are on a am64 cpu platform, cannot run this image reliably, it will either fail or take extremely long for tests to finish due to docker emulation on host between cpu archs.What would you like to see?
when you tag system-test repo, it will build and push a multi-platform docker manifest that has both a linux/amd64 and linux/arm64 version within, refer to quickstart for examples of how it accomplishes building same multi-platform manifests.
What alternatives are there?
manually build the arm64 on an arm64 host like a mac m1, then push that image manually to same repo.
The text was updated successfully, but these errors were encountered: