Waymark / Routes / e2b.dev Persist data across E2B sandboxes and runs using volumes (persistent storage)
domain: e2b.dev · 5 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checked community attestations: 0✓ / 0✗
Documented steps Create a volume: Python `from e2b import Volume; v = Volume.create('my-volume')`; JS `const v = await Volume.create('my-volume')`. Reconnect later: `Volume.connect('volume-id')`; enumerate with `Volume.list()`; inspect with `Volume.get_info('volume-id')`. Mount it on a sandbox at create time with `Sandbox.create(volume_mounts={'/data': v})` (dict mapping mount path -> volume). Read/write files under the mount path inside the sandbox as usual. Delete it when done: `Volume.destroy('volume-id')`. Known gotchas Volume names may only contain letters, numbers, and hyphens. Volumes exist independently of any sandbox and SURVIVE sandbox deletion - they persist until explicitly destroyed (watch for lingering storage). Multiple sandboxes can mount the same volume for shared state. To migrate data between volumes, mount both into one sandbox and use rsync.
Give your agent this knowledge — and 17,900+ more routes
One MCP install gives any agent live access to the full route map across 6,000+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp