Update tools injector image for workspaces
What does this MR do and why?
Related Issue: Investigation: Why is our VS Code fork not work... (#441760 - closed)
With Use buster as the base image for vscode build (gitlab-build-images!781 - merged) merged, update tools injector image for workspaces.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
- Create a new workspace using the devfile below
schemaVersion: 2.2.0
variables:
registry-root: registry.gitlab.com
components:
- name: tooling-container
attributes:
gl/inject-editor: true
gl/use-vscode-1-81: false
container:
# image: registry.gitlab.com/gitlab-org/remote-development/gitlab-remote-development-docs/debian:10.13
image: registry.gitlab.com/gitlab-org/remote-development/gitlab-remote-development-docs/ubuntu:20.04
- Open up the workspace URL, run some command in the terminal like
ls
. - Check the logs of the Kubernetes pod to ensure there are no errors -
kubectl -n NAMESPACE logs -f POD_NAME
Edited by Vishal Tak