2024-03-01T16:08:54.761577365Z [FATAL tini (6)] exec docker failed: No such file or directory Error
Hey folks I'm having trouble running my image on Runpod. My image works properly on a normal root access Docker environment but doesn't work on the Runpod template structure. It's my first time on Runpod, can anyone help out?
21 Replies
what is the error
In the post title:
You probably need a CUDA base image for starters
Try this.
You don't need
EXPOSE, add the ports to your template/pod@ashleyk The cuda base image worked, thank you so much!
2024-03-01T18:56:20.332807898Z /opt/nvidia/nvidia_entrypoint.sh: line 67: exec: docker: not found any idea about this one?
Where do you see this? Are you trying to run it from within your start.sh script?
Here it is @ashleyk
Did you set a docker start command for your pod or something?
@ashleyk , you are right. The default run script was working. I edited it, and now it's up and running.
Last question: I have an endpoint that listens on port 8081. When I send a request, I can't reach the port and can't get results.
How I should configure template config, below on image?
1. Make your app bind to
0.0.0.0 and not 127.0.0.1.
2. Add HTTP port 8081 to your pod, or alternatively a TCP port if there is a possibility that your request execution time will exceed 100s.
I see you already added it as a TCP port. TCP ports require a public IP, so if you are using Community Cloud, you need to ensure that you check the Public IP filter at the top of the page.
Then you need to go to the Connect button TCP port mappings and get the external port mapping and use the external port. 8081 will be the internal port.I'm using secure cloud, when I remove TCP port I'm losing public ip
I always add at least port 22 for SSH access.
This is the last config, still can't reach the port. I checked it with telnet. Am I missing something? @ashleyk
@ashleyk
You probably didn't bind your app to
0.0.0.0 like I said above
it can't work if it binds to 127.0.0.1.@ashleyk it's already 0.0.0.0
What port did you telnet to?
8081?
No, wrong, see above.
https://discord.com/channels/912829806415085598/1213184975629717525/1213203762621980743
Use EXTERNAL port NOT the internal one.
okay but the endpoint is working on 8081, how am ı going to hit it? Should i bind it to 8081?
No, bind it to 0.0.0.0
Hit it by connecting to EXTERNAL PORT.
Use TCP port mapping, or else change it to an HTTP port and use the proxy URL
You CANNOT connect to 8081, its impossible. EXTERNAL PORT only. NOT INTERNAL.
solved, thanks for your support!! @ashleyk
Glad you got it working 🥳