<!--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=509983) </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 When creating a workspace, we use a container image(e.g. `registry.gitlab.com/gitlab-org/workspaces/gitlab-workspaces-tools:9.0.0`) to inject various tools inside the container where we want to start the IDE. As a user(administrator), I want a way to configure this image to ensure Workspaces works properly is an isolated/offline environment. Duplicate issues - https://gitlab.com/gitlab-org/gitlab/-/issues/507857#note_2452111825 - https://gitlab.com/gitlab-org/gitlab/-/issues/508162+ ## Acceptance criteria TODO: Fill out (required) - [ ] [Describe what must be achieved to complete this issue.] - [ ] [If applicable, please provide design specifications for this feature/enhancement.] - [ ] [If applicable, please list any technical requirements (performance, security, database, etc.)] ## 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 -->