0.18.5rc1

This is a release candidate build of the upcoming 0.18.5 release. Read below to learn about its new features and bug-fixes.

Volumes

When you run anything with dstack, it allows you to configure the disk size. However, once the run is finished, if you haven't stored your data in any external storage, all the data on disk will be erased. With 0.18.5, we're adding support for network volumes that allow data to persist across runs.

Once you've created a volume (e.g. named my-new-volume), you can attach it to a dev environment, task, or service.

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

The data stored in the volume will persist across runs.

dstack allows you to create new volumes and register existing ones. To learn more about how volumes work, check out the docs.

Important

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

PostgreSQL

By default, dstack stores its state in /root/.dstack/server/data using SQLite. With this update, it's now possible to configure dstack to store its state in PostgreSQL. Just pass the DSTACK_DATABASE_URL environment variable.

DSTACK_DATABASE_URL="postgresql+asyncpg://myuser:mypassword@localhost:5432/mydatabase" dstack server

Important

Despite PostgreSQL support, dstack still requires that you run only one instance of the dstack server. However, this requirement will be lifted in a future update.

On-prem clusters

Previously, dstack didn't allow the use of on-prem clusters (added via dstack pool add-ssh) if there were no backends configured. This update fixes that bug. Now, you don't have to configure any backends if you only plan to use on-prem clusters.

Supported GPUs

Previously, dstack didn't support L4 and H100 GPUs with AWS. Now you can use them.

Full changelog

• Support dstack volumes by @r4victor in #1364
• Filter pool instances with respect to volumes availability zone by @r4victor in #1368
• Support AWS L4 GPU by @jvstme in #1365
• Add Concepts->Volumes by @r4victor in #1370
• Improve Overview page by @r4victor in #1377
• Add volumes prices by @r4victor in #1382
• Wait for GCP VM no capacity error by @r4victor in #1387
• Disallow mounting volumes inside /workflow by @r4victor in #1388
• Support NVIDIA NVSwitch in dstack VM images by @jvstme in #1389
• Optimize loading dstack Docker images by @jvstme in #1391
• Improve Contributing by @r4victor in #1392
• Support running dstack server with Postgres by @r4victor in #1398
• Support H100 GPU on AWS by @jvstme in #1394
• Fix possible server freeze after pool add-ssh by @jvstme in #1396
• Add OCI eu-milan-1 region by @jvstme in #1400
• Prepare future OCI spot instances support by @jvstme in #1401
• Remove if backends configured check by @r4victor in #1404
• Include project_name in Instance and Volume by @r4victor in #1390

See more: 0.18.4...0.18.5rc1