13 Replies
What kind of pod is this?
gpu
What template is it running?
Custom template
Then you need to add TCP port 22 to your template, and also ensure that your Docker image installs openssh-server and starts the sshd service.
We have used that Docker image before and we could connect easly
Did you check the public IP filter at the top of the page to ensure that your pod gets a public IP?
is pod started or its loop on container start
We use secure cloud
it started, right now is we restarted him
Is it constantly restarting in the container logs?
No
At the start everything is started
and we cant connect
now we did some changes to template, and pod is still downloading resources
but problem is that we could not connect when pod is started
Honestly, this feels like a bug with a custom template. If you are using a runpod template as a base, works fine, so it makes me suspect something about calling your openssh etc isn't being called properly. Can add some internal logs to validate.
Wouldn't make sense ssh just breaks down for a custom template but nothing else, cause I use a lot of custom templates too
Yep, I fully agree