Open mkandes opened 7 months ago
This would only be useful if jupyter
was installed outside of a container, which is a pretty niche use case. While it could be supported, it is less clear if this could cause other issues when interacting with containers and the filesystems on the login nodes. At this time, --disable-checklist
is a sufficient work-around already in place. Do we want to encourage users to place jupyter
outside of their containers?
This functionality may be useful when mixing the use of conda environments installed externally from a container. e.g., a likely RStudio use case.
@kenneth59715 suggested adding the user-specified --bind mounts to the when the pre-launch checklist runs
jupyter --version
to determine ifjupyter
is available from the containerized environment.