37 Replies
Well you simply start jupyter using the template
Where is the option?
try browsing how to start jupyter
i try not to spoonfeed
runpod pytorch template has it enabled
It wont start for me. I am using runpod/pytorch:2.2.0-py3.10-cuda12.1.1-devel-ubuntu22.04 as container image
is docker_args cmd?
is it working if you create from the UI?
It doesn't work if you override the docker start command, it gets started in the docker start command
You need to add this to start it:
https://github.com/runpod/containers/blob/main/container-template/start.sh#L73-L82
GitHub
containers/container-template/start.sh at main · runpod/containers
🐳 | Dockerfiles for the RunPod container images used for our official templates. - runpod/containers
its in
/start.sh
He overrode it
does && works there?
like maybe sh /start.sh && that command
No
start.sh has
sleep infinity
so anything after that will never runoh ya...
maybe call that first, if it doesn't have sleep
Have to either do it BEFORE or just include it in his override script
The script I used for overriding is the same as start.sh
I modified it to add a few commands such as install nano and screen
yes. It works if I deploy a pod from UI console
Show container logs
So there is start jupyter command there in your script?
Where's start jupyter function
I think he removed it
I think so
um.. its right there below setup_ssh
below setup_ssh
The variables are being exported, ssh web terminal is working
Is there an issue with
I cannot see "Starting Jupyter Lab..." in the logs
Yes, try adding
JUPYTER_PASSWORD
environment variable to your pod.
It won't start unless the environment variable is present.
Looks like start_jupyter
may be missing from the Python SDK, seems to only have start_ssh
and not start_jupyter
to automatically inject the environment variable.How to get the password?
Make up one and add it to the
JUPYTER_PASSWORD
environment variable on the pod.it is auto generated if you create via ui i think
He created pod using SDK
Yep
Done. It is working now
Yes. There was
start_ssh
as a boolean but no start_jupyter
Grand, you may want to consider logging a GitHub issue to add support for
start_jupyter
https://github.com/runpod/runpod-pythonGitHub
GitHub - runpod/runpod-python: 🐍 | Python library for RunPod API an...
🐍 | Python library for RunPod API and serverless worker SDK. - GitHub - runpod/runpod-python: 🐍 | Python library for RunPod API and serverless worker SDK.
Okay, will do that
There is already an issue for this:
- https://github.com/runpod/runpod-python/issues/311
Also, I've just submitted a pull request with a fix for this:
- https://github.com/runpod/runpod-python/pull/328
We'll wait for the maintainers to review, and if satisfactory, hopefully it'll be in the next release.
GitHub
Enable startJupyter in create_pod() · Issue #311 · runpod/runpod-py...
Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] Currently it is only supported to pas...
GitHub
Add start_jupyter argument to create_pod argument, to launch a note...
This PR resolves Issue #311 .
There is a design choice made here to be considered. It would be helpful to receive feedback on this, if another solution is preferred.
For jupyter to launch, it req...
@Asad Jamal Cognify
Jupiter is thing that needs to be first preinstalled on container level