You deployed the SpotWarp recipe. Connect the SpotWarp client on your own machine, and your container's /workspace is backed up continuously and restored onto the replacement node automatically, with your job restarted for you.
The container holds no storage credentials at all. Your own machine pulls the workspace over SSH, and your SaladCloud API key never leaves that machine.
Checkpoints and model weights land on your own disk, not in a third-party bucket. No storage account, no sync code, no storage bill.
When the node is lost, SpotWarp restores /workspace onto the replacement node in the same container group and runs your resume command.
With a standby replica running, our live test on October 21, 2026 restored the workspace and restarted the job in 17.1 seconds (one run, 5 MB checkpoint).
curl -fsSL https://gpu-action.com/install.sh | bashirm https://gpu-action.com/install.ps1 | iex
pip install --upgrade spotwarpspotwarp init
It asks for your SaladCloud API key, organization and project, and the container group to protect. Press Enter at the license prompt to use the 14-day evaluation. Everything is saved on your machine only.
spotwarp start -d --container <container-group-name> \ --resume-cmd "python3 /workspace/train.py --resume"
Check it any time with spotwarp status. Backups land in ./backups/<container-group-name>/ on your machine.
/workspace and resume from the latest one. SpotWarp moves and restores them for you.--no-standby to keep one replica; recovery then waits for SaladCloud to allocate a new node.