Serverless Unable to SSH / Use Jupyter Notebook Anymore
When I used to use Runpod when I first started, if I had an active worker, I could ssh / use a jupyter notebook if I had ssh open / notebook launched on the pod.
But now when I try to ssh, it just throws me an error:
My script is set up btw using Runpod's own start.sh script to start up jupyterlabs + openssh + call my handler.py:
https://github.com/justinwlin/Runpod-OpenLLM-Pod-and-Serverless/blob/main/start.sh
And everything in logs look correct. I think the reason why is I can't in my serverless template define an HTTP port / TCP port anymore. So has runpod just deprecated this moving forward?
GitHub
Runpod-OpenLLM-Pod-and-Serverless/start.sh at main · justinwlin/Run...
A repo for OpenLLM to run pod. Contribute to justinwlin/Runpod-OpenLLM-Pod-and-Serverless development by creating an account on GitHub.
5 Replies
This means your private key can't be found on your Mac, not a RunPod issue.
Interesting huh. Ill try again 🤔 on monday then, i could do it with gpu pod so i just assumed, good to know tho~
guess the http part is just not possible now tho 😦 prob dont let us control the ports on those anymore
I never use http ports in serverless so wouldn't know about that... your SSH private key can't work in GPU cloud either, the private key is the same regardless of GPU cloud or serverless so maybe you're using a different key for GPU cloud or something.
Hm. I guess I just copy whatever the Runpod connect option said, Ill take a closer look, thanks!
AH! Thank you @ashleyk I think ik why actually when checking my env variables.. It's cause for GPU Pod Runpod injects the Public Key env variable automatically into GPU Pods when you start up; but don't do it for Serverless functions. ;D; so as you said, i was trying to connect with ssh when the serverless function has zero clue what keys looking for
I was just dumb for never questioning why GPU Pods were able to get my public keys but serverless wasn't cause i didn't check properly 👁️
Doesn't explain why it couldn't find your private key on your local machine though.