Skip to main content
The examples on this page omit auth. To authenticate with your W&B API key, install cwsandbox[wandb] and pass auth=AuthStrategy.WANDB to Sandbox.run(), Sandbox(), or Sandbox.session(). See Get started.
Un volume est un espace de stockage qu’un sandbox monte à l’emplacement de votre choix. Les volumes temporaires appartiennent à un seul sandbox et disparaissent avec lui. Cette page s’adresse aux développeurs dont le sandbox doit écrire plus de données que ne peut en contenir le système de fichiers de son conteneur. À la fin de cette page, vous saurez attacher un volume temporaire.

Scratch volumes

A scratch volume is created with the sandbox and destroyed with it. Declare one with ScratchVolumeOptions in the volumes list.
ScratchVolumeOptions accepts the following fields:

Choose a storage medium

StorageMedium.DISK backs the volume with local disk. StorageMedium.MEMORY backs it with tmpfs, which is faster but counts against the mounting container’s memory request and against the policy’s memory ceiling. Because an unbounded RAM-backed volume could exhaust the node, a MEMORY volume must declare a size. It may do so as an absolute quantity, or as an integer percentage of the sandbox’s resolved memory request, such as "50%". The percentage form is valid only for MEMORY. A DISK volume must use an absolute size.

Mount a scratch volume on several containers

mount_path is a convenience that mounts the volume on the primary container. In a multi-container sandbox, omit mount_path and declare the mounts on each container instead, so that more than one container can reach the same volume.
For more on related sandbox features, see the following resources:
Dernière modification le 30 septembre 2026