Tooling container `$PATH` is overridden

[l0rd]

Describe the bug

The container quay.io/mloriedo/cloud-dev-images:golang has the following $PATH:

/go/bin:/usr/local/go/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

but after using it as a tooling container of a Che workspace the $PATH becomes:

/checode/checode-linux-libc/ubi9/bin/remote-cli:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games

The consequence is kind of drastic as I cannot use go:

$ go version
bash: go: command not found

Che version

next (development version)

Steps to reproduce

https://che-dogfooding.apps.che-dev.x6e0.p1.openshiftapps.com/#https://github.com/l0rd/cloud-dev-images?image=quay.io/mloriedo/cloud-dev-images:openjdk&che-editor=che-incubator/che-code/insiders

Expected behavior

The folders in the original $PATH should still be in the workspace $PATH.

Runtime

OpenShift

Screenshots

No response

Installation method

OperatorHub

Environment

Amazon

Eclipse Che Logs

No response

Additional context

No response

[RomanNikitenko]

@ibuziuk I don't know if it's related to VS Code side or operator area, but anyway we should take it for an investigation.

[RomanNikitenko]

I did the following:

• started Che-Code in quay.io/mloriedo/cloud-dev-images:golang container using port-forwarding (so - no dashboard, no operator)
• then checked PATH

it was overridden:

[RomanNikitenko]

btw: PATH has correct value when I create a terminal using Terminal => New Terminal (select a Container)