Error: /var/lib/domino/launch/command.sh: line 124: /opt/domino/workspaces/<IDE>/start: No such file or directory

Version/Environment (if relevant):

Domino 4.x and higher

Issue:

Your workspace fails to launch and you run into this error in the User logs:

Example of the full error when using Jupyter:

/var/lib/domino/launch/command.sh: line 124: /opt/domino/workspaces/jupyter/start: No such file or directory
Evaluating cleanup command on EXIT with exit code 127: ${CURL} --silent --show-error -X POST http://localhost:9000/executor/endSingleRun/63c33e1320e10e12089c2440?exitCode=$code_at_exit
Failed with exit code: 127

JupyterLab:

/var/lib/domino/launch/command.sh: line 124: /opt/domino/workspaces/jupyterlab/start: No such file or directory

VS Code:

/var/lib/domino/launch/command.sh: line 124: /opt/domino/workspaces/vscode/start: No such file or directory

Workspace UI error: 

The UI shows Failed to startalong with the status message: Your session closed unexpectedly. Don’t worry, your results and work have been saved.

Root Cause:

This error occurs when the start line for the IDE in the Pluggable Workspace Tools in the environment's definition is outdated and pointed at the wrong place. These definitions changed slightly from older versions of Domino.

Resolution:

Update the start line for the IDE in the environment's Pluggable Workspace Tools, e.g.:

Jupyter: start: [ "/var/opt/workspaces/jupyter/start" ]

Jupyterlab: start: [ /var/opt/workspaces/Jupyterlab/start.sh ]

VS Code: start: [ "/var/opt/workspaces/vscode/start" ]

The latest version of the complete Pluggable Workspace Tools is available in our doc: Add Workspace IDEs

jupyter:
  title: "Jupyter (Python, R, Julia)"
  iconUrl: "/assets/images/workspace-logos/Jupyter.svg"
  start: [ "/var/opt/workspaces/jupyter/start" ]
  httpProxy:
    port: 8888
    rewrite: false
    internalPath: "/{{ownerUsername}}/{{projectName}}/{{sessionPathComponent}}/{{runId}}/{{#if pathToOpen}}tree/{{pathToOpen}}{{/if}}"
    requireSubdomain: false
  supportedFileExtensions: [ ".ipynb" ]
jupyterlab:
  title: "JupyterLab"
  iconUrl: "/assets/images/workspace-logos/jupyterlab.svg"
  start: [  /var/opt/workspaces/Jupyterlab/start.sh ]
  httpProxy:
    internalPath: "/{{ownerUsername}}/{{projectName}}/{{sessionPathComponent}}/{{runId}}/{{#if pathToOpen}}tree/{{pathToOpen}}{{/if}}"
    port: 8888
    rewrite: false
    requireSubdomain: false
vscode:
  title: "vscode"
  iconUrl: "/assets/images/workspace-logos/vscode.svg"
  start: [ "/var/opt/workspaces/vscode/start" ]
  httpProxy:
    port: 8888
    requireSubdomain: false
rstudio:
  title: "RStudio"
  iconUrl: "/assets/images/workspace-logos/Rstudio.svg"
  start: [ "/var/opt/workspaces/rstudio/start" ]
  httpProxy:
    port: 8888
    requireSubdomain: false

Notes/Information:

Related article: 404 errors during Running phase of newly launched workspaces