<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=550128) </details> <!--IssueSummary end--> MR: Pending <!-- NOTE: For context on MR heading, see: https://handbook.gitlab.com/handbook/engineering/devops/dev/create/remote-development/index.html#relationship-of-issues-to-mrs --> ## Description Follow from the discussion here, https://gitlab.com/gitlab-org/gitlab-build-images/-/merge_requests/905#note_2566824178, we plan to provide full support for `linux/arm64`, which includes vscode fork build, workspace default image, and workspace tooling image. We should exec in this sequence, 1) vscode fork build for arm64 2) workspace tools image for arm64 3) default image for arm64 Then we update GitLab repo altogether with ARM64 support. And also update workspace docs for related information. For vscode fork build, the idea is to use one arm64 base image and build vscode fork on top of it. And pls see this issue for more details, https://gitlab.com/gitlab-org/gitlab-web-ide-vscode-fork/-/issues/53+ For tools image and default image, we should extend our current job in `gitlab-build-images`, and also resolve any potential issues raised with arm64 build. <!-- TODO: What kind of issue is this? Please uncomment and include one of the following: /label ~"type::feature" /label ~"type::bug" /label ~"type::maintenance" --> <!-- OPTIONAL: Is this a feature/enhancement? - Please describe the impact this feature/enhancement will have on the user experience and/or the product as a whole. - Provide a user story to illustrate the use case for this feature/enhancement. Include examples to help communicate the intended functionality. --> <!-- OPTIONAL: Is this a bug? Please uncomment and include the following: - **Current behavior:** - **Expected behavior:** - **Steps to reproduce:** - **Additional information:** please include VSCode version, browser dev tool logs, etc that might be helpful to debug the issue! --> ## Acceptance criteria - [ ] Update tools image fetch asesst script to download for both `linux/arm64` and `linux/amd64` - [ ] Update tools image CI to build for both platforms, and resolve any raising issues - [ ] Update workspace default image to build for both platforms, and resolve any raising issues - [ ] Update GitLab repo to remove image digest, and use image tag instead, so docker could decide to pull ARM64 or AMD64 - [ ] Test locally it works fine for ARM64, and also existing AMD64 works fine as well - [ ] Update our doc to indicate both support, the requirement section, and more ## Implementation plan TODO: Fill out or delete (optional) [Provide a high-level plan for implementation of this issue, including relevant technical and/or design details.] <!-- NOTE: Feel free to expand with more sections and headers as needed --> <!-- DO NOT TOUCH BELOW -->