Build the workspaces-tools image for linux/arm64
What does this MR do?
Stage ② of arm64 GitLab Workspaces (gitlab#550128): build the workspaces-tools image for linux/arm64 in addition to linux/amd64, now that gitlab-web-ide-vscode-fork!136 (merged) (merged) produces native linux-arm64 server builds.
.gitlab/ci/custom.images.yml:PLATFORM: 'linux/arm64,linux/amd64'onworkspaces-tools(same pattern asworkspaces-basein this file;.build_static_imagealready passes--platform=${PLATFORM}to buildx).scripts/workspaces-tools/fetch_assets.sh: downloads assets once per configured platform into.build/assets/<platform>— the layoutDockerfile.workspaces-toolsalready expects (itsCOPYinstructions areTARGETPLATFORM-parameterized, so the Dockerfile needs no changes). Tag-based downloads now address the server tarball by its deterministic file name via the generic package registry (vscode-reh-web-<target>-<tag>.tar.gz) instead of scraping a single positionalpackage_filesURL, which cannot distinguish architectures. Job-based downloads (GITLAB_VSCODE_FORK_JOB_ID/GITLAB_VSCODE_FORK_JOB_FILE_PATH) stay single-platform — a job artifact is built for one architecture — and the script now refuses the ambiguous combination with a multi-platformPLATFORM.README.md: documents settingPLATFORMon manual job-based triggers.
Merge readiness
Initially Draft pending a fork release with native arm64 builds. That release now exists — 1.94.0-1.0.0-dev-20260915124137 (thanks @ealcantara) — and this MR pins GITLAB_VSCODE_FORK_TAG to it, so the merge-order concern from review is resolved. The MR also pins BUILD_ARG_ALPINE_VERSION: '3.22' to fix a pre-existing master breakage surfaced by the first manual workspaces-tools run: the repo-global GOLANG_VERSION/ALPINE_VERSION pair had drifted to golang:1.26-alpine3.21, a tag Docker Hub never published (golang:1.26-alpine3.22 verified to exist for arm64 and amd64).
Testing
fetch_assets.sh was exercised end-to-end in a debian:bookworm container:
-
Tag route,
PLATFORM=linux/arm64,linux/amd64(tag1.94.0-1.0.0-dev-20251209191616): both platform dirs populated with server tarball + both extensions;fileconfirmslinux/arm64'snodeisELF aarch64andlinux/amd64's isx86-64— the right tarball lands in the right directory. -
Multi-platform
PLATFORM+ job variables: refused with exit 1 and an explanatory error. -
Job route,
PLATFORM=linux/arm64+ job16307470784(the greenbuild-server-arm64job from gitlab-web-ide-vscode-fork!136 (merged)): downloads and extracts,nodeisELF aarch64— this is exactly the manual-trigger test flow from the README. -
Release verification (2026-09-16): the published
vscode-reh-web-linux-arm64-1.94.0-1.0.0-dev-20260915124137.tar.gzfrom the new tag was audited withfile(1):node, all*.nodemodules (node-pty, spdlog, @parcel/watcher, kerberos, native-watchdog, deviceid) andripgrep/bin/rgareELF aarch64; highest referencedGLIBC_symbol is 2.28. The fetch script was re-run end-to-end in a container against this tag forPLATFORM=linux/arm64,linux/amd64: correct per-arch tarball in each platform directory.
The runtime quality of the arm64 server bits themselves is attested in gitlab-web-ide-vscode-fork!136 (merged)'s description (ELF audit + REH server runtime test on Debian 10/glibc 2.28 on arm64 and amd64 hardware).
Follow-ups after this merges
Stage ③ (default workspace image arm64) and stage ④ (Rails image digest pins in workspace_operations_constants.rb) per gitlab#550128.
/cc @vtak @zhaochen_li @ealcantara
Related: !1111 (merged) (multi-arch gitlab-vscode-build CI image, merged), gitlab-org/workspaces/gitlab-workspaces-proxy!52 (merged).