- Fork Sandboxes to test different variations of code
- Initialize Sandboxes with existing state for faster cold starts
- Save a reproducible environment you can return to later
create_image_from_filesystem() returns an image ID for Image.from_id; snapshot_memory() returns a checkpoint ID for create_from_memory_snapshot. They are not interchangeable.
Wait for writes and initialization to finish before capturing state. Mounted volumes and durable disks have their own persistence behavior; a reusable root-filesystem image is not a backup of every mounted dataset. See durable disks.
Storage is not billed yet. Planned pricing is $0.0001 per GB-hour of data stored, with no free allowance.This will use the same usage credits as compute and cover retained VM disk, volume, and snapshot data, including while compute is stopped. Empty disk capacity, shared base images, and internal copies are excluded. 1 GB = 1 billion bytes.
Creating a Filesystem Snapshot
Using Filesystem Snapshots
You can use Snapshots as a base image for any other abstraction or Sandbox on Beam, usingImage.from_id:
Creating a Memory Snapshot
You can also create a memory snapshot of a running Sandbox, which captures the sandbox’s process state and filesystem on supported runtimes. Restored sandboxes receive their own identity and URLs; inspectlist_urls() on the restored instance.
Using Memory Snapshots
You can use memory snapshots as a starting point for a new Sandbox, usingSandbox().create_from_memory_snapshot: