Open bmacauley opened 3 months ago
Thank you for your report, @bmacauley! We had the same issue reported earlier (see https://github.com/temporalio/docker-builds/issues/213) and pushed new images for the affected tags. Could you verify? (you might have to run docker rmi
to clear the image from your cache)
This is still happening with temporalio/admin-tools:1.24.2-tctl-1.18.1-cli-0.13.0
, which is the default version used by the helm chart.
^ the admin-tools not working on arm64
Seems like a few image tags are still affected including 1.22.7.1.
Expected Behavior
temporal on arm64 Linux is working correctly
Actual Behavior
temporal on arm64 Linux is not working correctly I believe the binaries are amd64 binaries
Steps to Reproduce the Problem
I am setting up temporal on k3s on ubuntu 2204 in Multipass on a Mac M1. architecture
ubuntu@temporal:~$ uname -m aarch64
2.After running helm to deploy the temporal on k3s, I get crashloopbackoff errors on some of the containers
running correctly... temporal-admintools temporal-web
crashloopbackoff... temporal-frontend temporal-history temporal-matching temporal-worker
error message....
/etc/temporal/start-temporal.sh: line 16: /usr/local/bin/temporal-server: cannot execute binary file: Exec format error
The correct arm64 containers are being pulled
working.... tctl temporal
not working... tdbg temporal-cassandra-toll temporal-sql-tool
temporal-sql-tool bash: /usr/local/bin/temporal-sql-tool: cannot execute binary file: Exec format error
i downloaded temporal-sql-tool to check it
ubuntu@temporal:~$ file temporal-sql-tool temporal-sql-tool: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, Go BuildID=YKktCnQevbFAZNSNLwHy/GM78rayp1t0RHnJ99Q3e/vpPHjRcqExXPiFanYzQs/XafXwTQ1y_JNzqzuhTvq, with debug_info, not stripped
It is an amd64 binary?
Specifications