Skip to main content
A running sandbox can be suspended: its state is serialized to disk and reconstructed on demand when you resume it. Nothing keeps running in between — there is no daemon or background process to manage.
Suspending only writes what changed since boot, which keeps the operation fast and the saved state small. Anything the guest held carries across, including variables set with env at creation. Pass env to Sandbox.resume only when you want to add or change one on the way back up.

Managing instances

sandbox.close() shuts down a running sandbox but leaves suspended instances untouched — use Sandbox.destroy(id) to remove them from disk.