-
Notifications
You must be signed in to change notification settings - Fork 766
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
Latest cadence images does not support amd64 architecture #5434
Comments
Hey while we are fixing this, you can use v1.2.5, it is published with linux/amd64 yesterday |
This was referenced Nov 22, 2023
the mention images are uploaded to dockerhub |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version of Cadence server, and client(which language)
This is very important to root cause bugs.
Describe the bug
A clear and concise description of what the bug is.
The latest cadence server images (1.2.2 and v1.2.4) are not published with
linux/amd64
architecture but withlinux/arm64
instead. It fails to execute the entrypoint exec command on my K8S cluster which run on amd64 nodes.To Reproduce
Is the issue reproducible?
Steps to reproduce the behavior:
A clear and concise description of the reproduce steps.
https://hub.docker.com/r/ubercadence/server/tags shows that the OS/ARCH for server
v1.2.4
and1.2.2
arelinux/arm64/v8
but in previous image versions it waslinux/amd64
:Trying to pull the
amd64
image without success:❯ docker pull --platform=amd64 docker.io/ubercadence/server:v1.2.4 v1.2.4: Pulling from ubercadence/server Digest: sha256:ffe1a74b7c189c8135592e931393e582c7008be0afcda648a5837f3c297179c4 Status: Image is up to date for ubercadence/server:v1.2.4 image with reference docker.io/ubercadence/server:v1.2.4 was found but does not match the specified platform: wanted linux/amd64, actual: linux/arm64/v8
Inspecting the pulled image also shows the arch is
arm64
:Expected behavior
A clear and concise description of what you expected to happen.
amd64
server images for1.2.2
andv1.2.4
should be published.Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here, E.g. Stackstace, workflow history.
The text was updated successfully, but these errors were encountered: