ARM64 containers reporting incorrect architecture as amd64

[blink-so]

Problem

Partner reported that exectrace containers for ARM64 (versions 1.0.1 and 1.0.0) are incorrectly reporting their architecture as amd64, causing exec format errors when deployed on ARM64 Kubernetes nodes.

Expected Behavior

ARM64 containers should report their architecture as arm64 and run successfully on ARM64 nodes.

Current Behavior

• ARM64 containers report architecture as amd64
• Results in exec format errors on ARM64 K8s clusters
• Affects versions 1.0.1 and 1.0.0

Container Registry

https://github.com/coder/exectrace/pkgs/container/exectrace

Analysis

The build system appears to compile for ARM64 correctly (GitHub Actions builds amd64, arm64, and armv7), but the issue may be in:

1. Container manifest creation
2. Image pushing process
3. Architecture metadata in the final images

The multi-arch manifest creation step in the release workflow may be failing or not properly tagging the ARM64 images.

Impact

Prevents deployment on ARM64 Kubernetes clusters for enterprise customers.

cc @UBWAH3YN7