Product
Snapshots
Pause a sandbox, snapshot it while it runs, commit it to an image, and restore it later, here or on another machine.
Pause and resume
$ smx pause <session> # suspend it in place; list shows PAUSED
$ smx resume <session> # continue it from where it stopped
Snapshot and restore
A snapshot captures disk and memory into an image reference; the sandbox keeps running. Restore boots a new session from it.
$ smx snapshot --session warm ghcr.io/me/warm:1 # sandbox keeps running
$ smx restore --image ghcr.io/me/warm:1 --session next
Restored sandboxes are reseeded so they never share random state.
Commit to an image
$ smx commit --session demo ghcr.io/me/demo:1
Restore on another machine
Memory restores on the machine that captured it and falls back to a disk boot elsewhere. Nodes that were tested to exchange memory join a class with --host-class <name>, and then restore each other's memory snapshots.
Policy comes along
Restored sandboxes still run under host-side policies and their security profile.
Related: Policies · Security model · Install