Why do some pods have a stop button and others only have a terminate button?
I noticed that when I create an on-demand post it sometimes has a stop button and sometimes not. When i attach network storage, there is not stop, only terminate. But without network storage there is a stop button. Is there additional info available on why the stop button is available only sometimes? Without a stop button the POD system software to need to be installed since the only option is to terminate and no pause/stop.
Solution:Jump to solution
When you’re using a network volume, we assume you’ll install and store everything in /workspace, so you technically don’t need to stop the pod separately, terminating it is effectively the same as stopping it.
8 Replies
Solution
When you’re using a network volume, we assume you’ll install and store everything in /workspace, so you technically don’t need to stop the pod separately, terminating it is effectively the same as stopping it.
That makes sense for storage, but are system libraries and updates installed to workspace? E.g. updates to comfyui, custom nodes, os updates for sftp access to the network storage, etc? When I terminate and restart, I need to reset up sftp access from scratch.
How would I restore the system state?
In that case, it’s better to create your own custom Docker image with everything pre-installed. you don’t have to set things up every time you start. The image should be ready to use as-is, without needing to install multiple things each time.
Will try that.. was hoping for a more hands free approach tho. Since if I create a docker, I could use AWS or GCP or so many other options vs RunPod
Like snapshots?, feel free to suggest anything in #🧐｜feedback
i guess, if it could simply have a stop option, it would solve the issue of system updates being retained
that would avoid creating, and publishing docker images
and be more standalone
so, if a stop option is available, i assume the system storage would be persistent until terminated. network volume could be added as needed.
I realize stop adds a storage cost, which is ok. but with a stop option, customers can decide to stop or terminate like they can for other pods that have that option - gives customers the choice
Snapshots could work, but then requires someone to remember to save each time vs. being automatic... im expecting stop / terminate to work like EC2 instances on AWS ... which i believe is how it works for Pods with a stop option
Because runpod uses docker containers it doesn't work like that, the other storage that you're seeing ( excluding volume disk on /workspace) is from a docker image, so I'd suggest to make a custom image for your own use so you don't have to reinstall system files everytime.
But if you want a vps like system I believe runpod can do it, just you have to rent a bare metal server for a long time
k, thanks!