[Bug] incorrect binary arch for arm64 image (1.22.7)

[raulsh]

What are you really trying to do?

We're running a Temporal cluster (1.22.7 version) in arm64 nodes in Kubernetes, but now is in a CrashLoopBack. And Docker image was pushed recently

Describe the bug

Kubernetes pod logs:

/etc/temporal/start-temporal.sh: line 16: /usr/local/bin/temporal-server: cannot execute binary file: Exec format error
/etc/temporal/start-temporal.sh: line 16: /usr/local/bin/temporal-server: No error information

Minimal Reproduction

I setup an ARM64 instance in AWS (t4g.medium) and then I pulled and ran the image:

Check if image is an arm64 image:

docker pull temporalio/server:1.22.7
docker inspect temporalio/server:1.22.7

Output (relevant part)

"Architecture": "arm64",
"Os": "linux",

And then check if is correct binary:

docker run --user=root --rm -it temporalio/server:1.22.7 -- bash

# inside container
apk add file
cd /usr/local/bin
file temporal-server

Output:

temporal-server: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, Go BuildID=Imr-tNox5hgSn4Jy-Qgu/soS56avX1TbsmBwYk3aP/MxLQlFW4shFul3i3GXr_/hy3teMO66aoy0IMWCGaU, with debug_info, not stripped

Environment/Versions

• OS and processor: t4g.medium instance (for reproduction), Kubernetes with ARM64 instances (r6g, m6g and c6g families)
• Temporal Version: 1.22.7
• Are you using Docker or Kubernetes or building Temporal from source? Docker and Kubernetes