-
Notifications
You must be signed in to change notification settings - Fork 911
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rollouts demo project containers are not built for arm64 #4125
Comments
I think the images come from this repo: https://github.com/argoproj/rollouts-demo probably has to be ran manually I don't see any github actions on that repo etc. |
yes please i'm facing the same challenge. |
https://github.com/argoproj/rollouts-demo/blob/master/release.sh is how that project seems to be built |
Hi @zachaller Thank you so much for the quick response. |
That repo will need modification to support different platforms, so you would need to modify it. You could also open a PR with the enhancement as well. |
I plan on taking a run at this this week or next. The shell script has
confused me a bit .. if I run it as an Actions job and generate two images
and a multiarch manifest, per colour, who can update the images in Docker
hub?
…On Mon, Feb 17, 2025, 10:10 Zach Aller ***@***.***> wrote:
That repo will need modification to support different platforms, so you
would need to modify it. You could also open a PR with the enhancement as
well.
—
Reply to this email directly, view it on GitHub
<#4125 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADSERMVE47OK5HFU6RJMND2QH3VLAVCNFSM6AAAAABW3WSZB2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRTGM4TQMZTHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
[image: zachaller]*zachaller* left a comment (argoproj/argo-rollouts#4125)
<#4125 (comment)>
That repo will need modification to support different platforms, so you
would need to modify it. You could also open a PR with the enhancement as
well.
—
Reply to this email directly, view it on GitHub
<#4125 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADSERMVE47OK5HFU6RJMND2QH3VLAVCNFSM6AAAAABW3WSZB2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRTGM4TQMZTHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Checklist:
Describe the bug
The quick start tutorials for the argoproj/argo-rollouts demo do not work on arm64 until at least v1.8.0. The issue is that the rollouts-demo container at https://hub.docker.com/r/argoproj/rollouts-demo is built only on amd64. I am not sure where the demo is built - if I did, I would happily submit some changes to build separate amd64 and arm64 images and create a multiarch manifest.
To Reproduce
To reproduce the bug, install Argo on a Kubernetes cluster running only arm64 nodes, install ArgoCD, and then attempt to walk through the rollouts demo. The rollout will fail because no container is available that can run on the nodes.
Expected behavior
As ArgoCD is supported on multiple architectures, I would expect the "Getting started" documents for it to also work across all supported architectures. I'm happy to help if pointed in the right direction.
Version
Attempted on argocd v1.8.0 - but this is true for all versions because it is not Argo, but the rollouts-demo container, that causes the issue.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered: