Skip to content


Volumes allow you to persist data between runs. dstack simplifies managing volumes and lets you mount them to a specific directory when working with dev environments, tasks, and services.


Volumes are currently experimental and only work with the aws backend. Support for other backends is coming soon.


First, create a YAML file in your project folder. Its name must end with .dstack.yml (e.g. .dstack.yml or vol.dstack.yml are both acceptable).

type: volume
name: my-new-volume
backend: aws
region: eu-central-1
size: 100GB

If you use this configuration, dstack will create a new volume based on the specified options.

Registering existing volumes

If you prefer not to create a new volume but to reuse an existing one (e.g., created manually), you can specify its ID via volume_id. In this case, dstack will register the specified volume so that you can use it with development environments, tasks, and services.


See the .dstack.yml reference for all supported configuration options and multiple examples.

Creating and registering volumes

To create or register the volume, simply call the dstack apply command:

$ dstack apply -f volume.dstack.yml
Volume my-new-volume does not exist yet. Create the volume? [y/n]: y
 my-new-volume  aws      eu-central-1  submitted  now     

When creating the volume dstack automatically creates an ext4 file system on it.

Once created, the volume can be attached with dev environments, tasks, and services.

Attaching volumes

Dev environments, tasks, and services let you attach any number of volumes. To attach a volume, simply specify its name using the volumes property and specify where to mount its contents:

type: dev-environment
ide: vscode
  - name: my-new-volume
    path: /volume_data

Once you run this configuration, the contents of the volume will be attached to /volume_data inside the dev environment, and its contents will persist across runs.


When you're running a dev environment, task, or service with dstack, it automatically mounts the project folder contents to /workflow (and sets that as the current working directory). Right now, dstack doesn't allow you to attach volumes to /workflow or any of its subdirectories.

Managing gateways

Deleting gateways

When the volume isn't attached to any active dev environment, task, or service, you can delete it using dstack delete:

$ dstack delete -f vol.dstack.yaml

If the volume was created using dstack, it will be physically destroyed along with the data. If you've registered an existing volume, it will be de-registered with dstack but will keep the data.

Listing volumes

The dstack volume list command lists created and registered volumes.


Using volumes across backends

Since volumes are backed up by cloud network disks, you can only use them within the same cloud. If you need to access data across different backends, you should either use object storage (or replicate the data across multiple volumes).

Using volumes across regions

Typically, network volumes are associated with specific regions, so you can't use them in other regions. Sometimes, volumes are also linked to availability zones, but some systems allow volumes that can be used across different availability zones within the same region.