Cannot connect to CPU pods
As titled.
The HTTP service doesn't work, and I can't start a web terminal neither
The HTTP service doesn't work, and I can't start a web terminal neither
S
Sclicking start web terminal does not work
Snormally, after clicking Start, the right botton will be activated
AProbably 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
S
S
S
SI also expose many ports for tcp connections
ALooks 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 or ? Connecting to the TCP ports won't work if they bind to , they have to bind to .
S
SI only modified this part
Scan I choose a base image like those for gpu pods? on cpu pod
S(as long as it will enable me to use jupyter
AYes but what is listening on those ports?
Ssome python program
Susing py-axon
ACheck this
AAlso make sure its listening on the random ports RunPod gave you not 70000 etc
SI don't quite get it.. Any more detailed doc i can refer?
JCorrect, @flash-singh we should allow our current torch template to also be selected for CPU. No need to add another one just for CPU.
Five edited the ubuntu template and took put juptyer port