Ignore root start.sh and use custom persistent script.
Im trying to avoid using start.sh since I need to experiment with some different processes.
I've tried to copy the contents of start.sh and to point via the container start command to a install_req.sh script that is in the workspace folder. Im also unchecking "start jupyter notebook" and "ssh terminal access" since I don't want the container to run the original start.sh file. Maybe here Im confusing how these work or Im missing something.
The logs show that all is good but I can't use the runpod ui to start jupyter anymore and the actual ssh connection does not work anymore. Why is that happening although install_req.sh is the same as start.sh in the root dir?
Also , I've noticed that in the start.sh, there are some references to a pre_start.sh and a post_start.sh script in the root but I can't find them.
I don't want to get into messing with docker just now.
Thank you.
I've tried to copy the contents of start.sh and to point via the container start command to a install_req.sh script that is in the workspace folder. Im also unchecking "start jupyter notebook" and "ssh terminal access" since I don't want the container to run the original start.sh file. Maybe here Im confusing how these work or Im missing something.
The logs show that all is good but I can't use the runpod ui to start jupyter anymore and the actual ssh connection does not work anymore. Why is that happening although install_req.sh is the same as start.sh in the root dir?
Also , I've noticed that in the start.sh, there are some references to a pre_start.sh and a post_start.sh script in the root but I can't find them.
I don't want to get into messing with docker just now.
Thank you.
