Skip to content

Publish amd64 and arm64 Docker images - #2614

Open
kmcginnes wants to merge 4 commits into
mainfrom
publish-arm64-images
Open

kmcginnes wants to merge 4 commits into
mainfrom
publish-arm64-images

Conversation

@kmcginnes

@kmcginnes kmcginnes commented Nov 14, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Docker on arm64, such as Apple Silicon, can't pull 3.3.1 or later, so the publish workflow now pushes real linux/amd64 and linux/arm64 images under every tag.

3.3.0 was a single amd64 image that arm64 Docker ran under emulation. From 3.3.1, the runner image moved from Ubuntu 24.04 to 26.04, and its docker build writes an image index with one amd64 image plus a provenance attestation entry. Docker on arm64 finds no matching platform in that index and refuses it. The workflow didn't change between the two releases. The runner logs show the switch: the 3.3.0 run says writing image sha256:…, and the 3.3.1 run says exporting attestation manifest and exporting manifest list.

 build_docker.yml
+  Set up QEMU (arm64)
+  Set up Docker Buildx
-  docker build, docker tag, docker push × 2
+  docker buildx build --platform linux/amd64,linux/arm64 -t <tag> -t sagemaker-<tag> --push
   release only:
-    docker tag, docker push × 2
+    docker buildx imagetools create -t latest -t sagemaker-latest <tag>

Both version tags come from one build, and imagetools create copies that index unchanged, so every alias keeps one digest.

 Dockerfile
-toolchain (Vite+ image)
-  build   ← toolchain, once per platform
-  deps    ← toolchain
+build  FROM --platform=$BUILDPLATFORM <Vite+ image>   # client bundle and scripts, built once, natively
+deps   FROM <Vite+ image>                              # prod install and the Node.js binary, per platform
 runtime (Amazon Linux 2023)
-  node ← build
+  node ← deps

The client build is the same on every platform, so it runs once on the runner's own platform. Under emulation it was the slowest stage. Only the prod install, the Node.js binary, and the runtime stage run per platform. Both base images already publish arm64 variants. The proxy server's prod dependencies have no native addons and no platform-specific packages.

--provenance=false alone would bring back the 3.3.0 shape: amd64 only, run under emulation on arm64. With a real arm64 entry, arm64 hosts pick it, so the attestations stay. QEMU in one job beat a native arm runner plus a merge job, since runners come from a shared pool and the emulated part is small.

test_build_docker.yml now also builds the arm64 image and checks its architecture, its Node.js version, /status, /explorer/, and that it listens on every interface. The wait for the server goes from 30 to 60 seconds, and the check for the listening log line now retries for up to 10 seconds, since under emulation the line can land after the server already answers. The binfmt and BuildKit images the two setup actions run are pinned by digest, like every other image and action here. Dependabot doesn't update those two pins.

Check the tag, version, and latest tags before publishing a release image (#2603) also changes the push steps of build_docker.yml. This PR touches only the build and push steps and adds the two setup steps before them, so whichever merges second rebases onto a small conflict. That PR's push loop becomes one buildx build with a -t per tag.

Evidence

Before: public.ecr.aws/neptune/graph-explorer:3.3.2 and latest are an image index with linux/amd64 and unknown/unknown only.
After: a local docker buildx build --platform linux/amd64,linux/arm64, pushed to a throwaway registry on 127.0.0.1, gave <version>, sagemaker-<version>, latest, and sagemaker-latest the same index digest, holding linux/amd64, linux/arm64, and two attestation entries.

Verified live: on an arm64 host, a --no-cache build of both platforms took 262 s before this change and 121 to 143 s after it, with amd64 emulated. Both images report Node.js v24.22.2 (arm64 and x64) and answer /status and /explorer/. The CI step scripts ran unchanged against the arm64 image. On this PR's first GitHub run of the Docker test workflow, the amd64 build took 69 s, the arm64 build under QEMU 4 min 2 s, and the whole job 6 min 15 s, inside its 15-minute limit. The publish job builds both platforms in one build, so it should take about as long as those two builds.

Merge Danger

Door: two-way

Impact: publishing

The next push to main publishes latest-SNAPSHOT as a two-platform index. Reverting goes back to amd64-only images.

Related


🤖 Written by an AI agent on my behalf.

@kmcginnes
kmcginnes marked this pull request as ready for review November 14, 2026 00:15

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docker image public.ecr.aws/neptune/graph-explorer:latest does not support Apple Silicon (linux/arm64) in versions 3.3.1 and 3.3.2

1 participant