Keeping reverse proxy hostname between destroy/start
Hello,
I'm using network storage for my pod. My use case doesn't require the container to be up 24/7. I noticed there was no stop button on the web GUI but I was able to start/stop container with the API. So I did. I think this is what could cause my pod to run without GPU attached. I found that I can only start the pod without GPU on the web GUI this morning.
I was trying to stop container instead of destroying it because I want to keep the same container id, so my reverse http proxy hostname doesn't change each time.
Is there a workaround?
Thanks.
Solution:Jump to solution
At this time there's no way to keep the same pod ID after you terminate a network volume pod - there's no stop state for network volume pods (it's really specifically designed for machine based storage so the storage can be kept and the GPU can be freed up)
I can definitely see how this would be a feature gap though so I will bring it up to the team...
2 Replies
Solution
At this time there's no way to keep the same pod ID after you terminate a network volume pod - there's no stop state for network volume pods (it's really specifically designed for machine based storage so the storage can be kept and the GPU can be freed up)
I can definitely see how this would be a feature gap though so I will bring it up to the team
@f4242
Unfortunately it doesn't appear this will be feasible to implement - we appreciate the feedback though