Cannot connect to CPU pods
As titled.
The HTTP service doesn't work, and I can't start a web terminal neither
16 Replies
clicking start web terminal does not work
normally, after clicking Start, the right botton will be activated
Probably using the Ubuntu template, which is pretty normal for CPU pods, I don't know why the template even exposes port 8888 when it doesn't even have Jupyter. cc: @Merrell
I also expose many ports for tcp connections
Looks like Jupyter isn't being installed in the Dockerfile for the base image, so that probably explains why HTTP port 8888 isn't working. Are the applications that you are running on all those TCP ports you exposed binding to
0.0.0.0 or 127.0.0.1 ? Connecting to the TCP ports won't work if they bind to 127.0.0.1, they have to bind to 0.0.0.0.
I only modified this part
can I choose a base image like those for gpu pods? on cpu pod
(as long as it will enable me to use jupyter
Yes but what is listening on those ports?
some python program
using py-axon
Check this
Also make sure its listening on the random ports RunPod gave you not 70000 etc
I don't quite get it.. Any more detailed doc i can refer?
Correct, @flash-singh we should allow our current torch template to also be selected for CPU. No need to add another one just for CPU.
ive edited the ubuntu template and took put juptyer port