Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Make jupyterlab default environment part of managed qhub-config.yaml environments
See original GitHub issueSummary
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
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@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.
Useful feature. Let’s keep this issue open.