Publish a multi-platform image (linux/amd64 + linux/arm64)
What does this MR do?
Publishes the proxy container image as a multi-platform manifest list (linux/amd64 + linux/arm64) instead of amd64-only.
- Dockerfile: builds with
--platform=$BUILDPLATFORMand cross-compiles viaTARGETOS/TARGETARCH. CGO is already disabled, so the Go build needs no emulation or per-arch toolchains. The runtime stage'sRUN chmodis replaced byCOPY --chmod=0755, so the foreign platform needs no QEMU either — the build is native-speed for both platforms. - scripts/build_and_publish_image.sh: uses
docker buildxwith adocker-containerbuilder to build and--pushboth platforms as one manifest list under the same tag.docker loginmoves before the build because--pushpublishes directly.--provenance=falsekeeps the pushed artifact a plain manifest list (avoids theunknown/unknownplatform entries some registry clients show for attestation manifests).
Consumers pull the same IMAGE_NAME:IMAGE_VERSION as today — amd64 users see no change; the same tag now also resolves on arm64 nodes.
Why?
The proxy is the only cluster-side Workspaces component without an arm64 image (agentk is already multi-arch), so on arm64 node pools (AWS Graviton, Azure Cobalt, …) it crashloops with exec format errors and operators must dedicate an amd64 node to it. This is complementary to the workspace-pod arm64 effort in gitlab-org/gitlab#550128 — the proxy is a plain CGO-free Go service, so its multi-arch build is independent of the VS Code fork work.
How to verify
docker buildx create --driver docker-container --use
docker buildx build --platform=linux/amd64,linux/arm64 --provenance=false -f ./Dockerfile .Both platforms build successfully (verified locally); with --push the result is a 2-entry manifest list.