pod with custom template have no tcp ports exposed
Hi,
I just created my custom template, and I set the ports to be exposed in the template, but after I deploy a pod, it has no ports exposed, did I configure something wrong?
5 Replies
from system log, i see it keeps starting container, is this expected?
or do i have to expose ports like 22, 3001 when building docker image?
No you dont have to, but something has to be listening to that port inside the pod, and the port that is exposed and the pod ip is in the connect button
And for stuck at start container is you have to run something(app, or something ) in your image or else it will be stuck in a bootloop, else just put sleep infinity in the docker command args
i see, so i can't just use CMD ["/bin/bash'] for my container?
btw, i'm looking at this https://github.com/runpod/containers , do I have to install nginx and openssh-server in my image?
GitHub
GitHub - runpod/containers: 🐳 | Dockerfiles for the RunPod contain...
🐳 | Dockerfiles for the RunPod container images used for our official templates. - runpod/containers
Just put sleep infinity in the end of it
Yes or just use runpod base image, pytorch, etc