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.
ボリュームとは、サンドボックスが指定したパスにマウントするストレージです。スクラッチボリュームは 1 つのサンドボックスに属し、そのサンドボックスが削除されると一緒に削除されます。 このページは、コンテナーのファイルシステムの容量を超えるデータをサンドボックスに書き込む必要がある開発者を対象としています。このページを読み終えると、スクラッチボリュームをアタッチできるようになります。

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:
最終更新日 2026年9月30日