#POD Duplication

11 messages · Page 1 of 1 (latest)

fresh wharf
#

I would like to duplicate an existing running Pod exactly as it is, including the current environment, installed packages, configurations, and attached storage setup.

Is there a way to clone or duplicate a running Pod into a new Pod without rebuilding the environment manually?

Ideally, I want the new Pod to be an identical copy of the current one so I can run both independently.

Could you please advise the recommended workflow for this?

soft pineBOT
wise muskBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

river pecan
#

there are several ways how to achieve this. The easiest one might be:

  • create your own template
  • either deploy identical pods with local storage or create two network storages
#
  • boot up both and use either rsync, runpodctl, croc or something similar to copy files from the original to the clone
#

with rsync you’d bw able to keep the files always in sync

#

there might be other solutions which could suite you more - sync data from pod1 to aws s3 bucket, google cloud, dropbox or whatever. Then use pod2 to download them. You can always sync data before shuting down or terminating the pods and re-sync files on both pods on deploy

#

You may also consider creating your own docker image - based in your future needs (if you anticipate you will need more of those clones in the future)

#

I have very little information to pick the best solution for you, might be you dont need a clone pod at all and serverless workers would do the job for you .. depends

#

you know you can go into details in our private conversation .)

#

oh, one more important thing @fresh wharf - you may want to choose the right template in this setup. A one which persists important data like root’s home folder, python venvs etc on /workspace. Otherwise you’ll need to configure and install few things after every restart. Can help you pick one based on your usecase