Building ARM64 Container Images When Upstream Doesn't Ship Them

Thu, 07 May 2026 00:00:00 +0000

A pod is CrashLoopBackOff with no application stack trace. The container manifest’s image field references an upstream tag that “should” work. The Docker pull succeeded. The container starts, exits with no log output, and restarts. The cause is almost always architecture: the image was published linux/amd64 only, the host is ARM64 (Apple Silicon, Graviton, Ampere), and the runtime is silently emulating — or failing to emulate — the binary. When upstream publishes ARM64 source artifacts but no ARM64 image, the fix is to build one.

Container-Images on Agent Zone

Building ARM64 Container Images When Upstream Doesn't Ship Them