-
Notifications
You must be signed in to change notification settings - Fork 880
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
kubectl-argo-rollouts arm64 docker image not working - Dashboard #1728
Comments
I think that we need to create/keep the ARM executable first. Doesn't look it is released by default argo-rollouts/.github/workflows/release.yaml Line 130 in 4c08f7e
|
True, the arm64 artifacts don't seem to be released, but the arm64 Docker images are released on Quay. The problem with those images seems to be in the Dockerfile of the plugin where it uses an amd64 base image: https://github.com/argoproj/argo-rollouts/blob/master/Dockerfile#L74 The root cause of this is probably deeper than that, but to me it seems like a good starting point |
…1728 (#1732) Signed-off-by: Charles Guertin <[email protected]>
When deploying this image: argoproj/rollouts-demo:blue on minikube cluster on MacBook air. Argo Rollouts Version - quay.io/argoproj/argo-rollouts:v1.6.6 |
@SahajMahajan the error probably means that the rollouts-demo is not compiled for mac/arm and has nothing to do with Argo Rollouts. You should open an issue at https://github.com/argoproj/rollouts-demo |
Summary
The arm64 version of the
quay.io/repository/argoproj/kubectl-argo-rollouts
Docker image isn't working.When running a container on my raspberry pi with the image tagged
v1.1.1
, I get the following error:Diagnostics
What version of Argo Rollouts are you running?
v1.1.1
The problem seems to be that
amd64
is hardcoded in the Dockerfile, here: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: