JetBrains IDE-based CDE should not depend on Node.js presence in a user's container #23174
Labels
area/editors
kind/enhancement
A feature request - must adhere to the feature request template.
severity/blocker
Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.
severity/P1
Has a major impact to usage or development of the system.
Is your task related to a problem? Please describe
When the user starts a workspace with a JetBrains IDE from the Dashboard,
they need to make sure Node.js is present in a
tools
container.Node.js is required to serve the stub web page that the Dashboard forwards to once the CDE is started:
This page also serves as an editor's
main
endpoint.This is not a problem when starting a CDE for JS development, because the
tools
container always includes Node.js.But when starting a CDE for Java development (e.g.
Spring Boot
stack) there's a low chance Node.js is present in atools
container.In this case, the Dashboard forwards to itself continuously when trying to open an editor page for such a CDE:
Screen.Recording.2024-10-01.at.14.00.31.mov
Describe the solution you'd like
The
editor-injector
init-container should bring the Node.js binaries with all the required libraries,and copy it to the
tools
container together with the editor binaries.Describe alternatives you've considered
The user always can open CDE from the JetBrains Gateway application:
As it doesn't depend on Che Dashboard.
Additional context
No response
The text was updated successfully, but these errors were encountered: