Make jupyterlab default environment part of managed nebari-config.yaml environments

[tylerpotts]

Summary

Currently the environment that jupyterlab launches with is built into the docker container that qhub launches with. This becomes an issue when users would like to modify the jupyterlab environment e.g. like PR #730. This would also reduce the size of the docker image speeding up the jupyterlab image launching.

Proposed implementation

The default jupyterlab environment will now be specified in DEFAULT_ENVIRONMENTS and the environment.yaml will be removed from the jupyterlab qhub image. There additionally needs to be a validation check to ensure that the default environment exists in the default environments.

Acceptance Criteria

• jupyterlab profile should launch normally

Tasks to complete

Related to

Closes #715

[github-actions]

This issue has been automatically marked as stale because there was no recent activity in 60 days. Remove the stale label or add a comment, otherwise, this issue will automatically be closed in 7 days if no further activity occurs.

[pierrotsmnrd]

Useful feature. Let's keep this issue open.

[iameskild]

Another related feature to consider is allowing users to install linux packages via qhub-config.yaml. Currently this handled in the Jupyterlab docker images (in apt.txt).

[trallard]

@iameskild does this need to remain open? seems this issue is now stale

[iameskild]

@trallard I would say that if we go with the RFD I proposed here (or some other variant), we won't need this since the user will be able to customize their jupyterlab image how they see fit.

[trallard]

Ok marking as blocked until we decide on the RFD

[dcmcand]

Closing because this is now possible using jhub-apps