apiserver arm64 image is broken: ships amd64 dockerize binary (Exec format error)
Author: anideebee7Created Jul 2, 2026Updated Jul 2, 2026
Bug
fonoster/apiserver:0.17.1 publishes a linux/arm64 manifest entry, but the image cannot start on arm64 hosts (tested on AWS Graviton / EKS):
sh: 1: dockerize: Exec format errorRoot cause
mods/apiserver/Dockerfile hardcodes the amd64 dockerize artifact:
&& wget https://github.com/jwilder/dockerize/releases/download/"$DOCKERIZE_VERSION"/dockerize-linux-amd64-"$DOCKERIZE_VERSION".tar.gz \
&& tar -C /usr/local/bin -xzvf dockerize-linux-amd64-"$DOCKERIZE_VERSION".tar.gz \So the arm64 build (via buildx/QEMU) embeds an x86-64 dockerize binary, and the entrypoint dies immediately. This is still present on main.
Suggested fix
Use buildx's TARGETARCH build arg (dockerize publishes linux-arm64 tarballs for v0.7.0):
ARG TARGETARCH
...
&& wget https://github.com/jwilder/dockerize/releases/download/"$DOCKERIZE_VERSION"/dockerize-linux-${TARGETARCH}-"$DOCKERIZE_VERSION".tar.gz \
&& tar -C /usr/local/bin -xzvf dockerize-linux-${TARGETARCH}-"$DOCKERIZE_VERSION".tar.gz \For reference: autopilot:0.17.1, dashboard:0.17.1, routr:v2.13.21, and asterisk:20 arm64 images all start fine on arm64 — apiserver is the only one affected (it is the only image that bundles dockerize).
Happy to open a PR if useful.
Source: fonoster/fonoster