-
Bug
-
Resolution: Done
-
Critical
-
3.3.0.GA
-
False
-
None
-
False
If VS Code is the default editor and I start a workspace using a devfile with one container (let's call it tooling), then VS Code won't be executed in the tooling container but in a container named che-code-runtime-description.
This behavior can be fixed renaming vscode as che-code:
oc exec -ti -n openshift-devspaces deployment/plugin-registry -- sed -i "s/ name: vscode/ name: che-code/" /var/www/html/v3/plugins/che-incubator/che-code/insiders/devfile.yaml
Note this problem is not reproducible with samples as, in that case, the DevWorkspace is pre-created at plugin-registry build time.
- is related to
-
CRW-3327 Unable to launch sample workspace with any IDE: "The workspace has not received an IDE URL in the last 20 seconds. Try to re-open the workspace."
- Closed
-
CRW-3098 Confirm how to refer to third party IDEs within Dev Spaces, and how/where to document licenses
- Closed
- relates to
-
CRW-3445 Starting a VS Code workspace: "/home/user/.bashrc: No such file or directory"
- Closed
- links to