how to run separate jupyter remote server for each notebook in a devcontainer? #11227
Unanswered
mkarikom
asked this question in
Questions and Answers
Replies: 1 comment
-
I've transferred this into an issue, we currently do not support such a feature, please follow the #11266 issue for further updates. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Background:
Sometimes it's nice to be able to explore two different versions of some code. In the notebook context (at least in vscode), this seems to require separate kernels. My understanding is that (at least in vscode), having two separate kernels requires two separate servers. For kernel persistence (remote connection here can be dodgy), these two servers are started as "remote servers" as below.
Issue (server for notebook 2 replaces server for notebook 1):
Note: this scheme already works great for the case with a single notebook/ jupyter server
For each of two notebooks, I open up a screen session and run the following (each kernel has a unique port):
jupyter notebook --no-browser --port=9996 --config=/workspaces/working_repo/.devcontainer/jupyter_notebook_config.json
jupyter notebook --no-browser --port=9997 --config=/workspaces/working_repo/.devcontainer/jupyter_notebook_config.json
Beta Was this translation helpful? Give feedback.
All reactions