Skip to content

Releases: dstackai/dstack

0.18.25

13 Nov 10:40
@r4victor r4victor
0.18.25
e8aebe8
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
0.18.25 Latest
Latest

Multiple volumes per mount point

It's now possible to specify a list of volumes for a mount point in run configurations:

...
volumes:
  - name: [my-aws-eu-west-1-volume, my-aws-us-east-1-volume]
    path: /volume_data

dstack will choose and mount one volume from the list. This can be used to increase GPU availability by specifying different volumes for different regions, which is desirable for use cases like caching. Previously, it was possible to specify only one volume per mount point, so if there was no compute capacity in the volume's region, provisioning would fail.

DSTACK_NODES_IPS environment variable

A new DSTACK_NODES_IPS environment variable is now available for multi-node tasks. It contains a list of internal IP addresses of all nodes in the cluster, e.g. DSTACK_NODES_IPS="10.128.0.47\n10.128.0.48\n10.128.0.49". This feature enables cluster workloads that require configuring IP addresses of all the nodes.

What's Changed

Full Changelog: 0.18.24...0.18.25

Contributors

un-def, r4victor, and deep-diver
Assets 2
Loading

0.18.24

08 Nov 09:43
@jvstme jvstme
0.18.24
537b43b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
0.18.24

Backward compatibility

This update includes a hotfix for a backward compatibility issue that prevented CLI v0.18.23 from working with older versions of the dstack server.

What's changed

  • Fix backward compatibility broken in 0.18.23 by @jvstme in #1974

Full changelog: 0.18.23...0.18.24

Contributors

jvstme
Assets 2
Loading

0.18.23

07 Nov 20:54
@jvstme jvstme
0.18.23
2912670
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
0.18.23

Gateway is optional

Previously, running any service required setting up a gateway. With this update, a gateway is no longer needed to run a service for development purposes.

Service endpoint

  • If no gateway is created, the service’s endpoint will be accessible at <dstack server URL>/proxy/services/<project name>/<run name>/.
  • If a service has a model mapping, the model will be accessible via the OpenAI-compatible endpoint at <dstack server URL>/proxy/models/<project name>/.

Note

While this change makes it much easier to use services for development, you will still need a gateway if you want to use a custom domain, enable HTTPS, or use auto-scaling.

Gateway property

If a gateway is created but isn’t needed for a service, set the gateway property to false. If you have multiple gateways, you can choose one by setting gateway to the name of the gateway.

Model mapping

If the model is in OpenAI format, you can now use a shorter syntax for model mapping—simply set the model property to the model's name.

type: service

image: ollama/ollama
commands:
  - ollama serve &
  - sleep 3
  - ollama pull llama3.1
  - fg
port: 11434

model: llama3.1

The longer syntax with more settings remains available.

Updating running services

Previously, updating a service’s configuration required restarting it. Now, you can update the replicas and scaling properties in place. Just run dstack apply, and the changes will take effect. New replicas will be created while the old ones continue running.

What's changed

New contributors

Full changelog: 0.18.22...0.18.23

Contributors

un-def, olgenn, and 5 other contributors
Assets 2
Loading

0.18.22

31 Oct 15:00
@jvstme jvstme
0.18.22
19cd2fd
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
0.18.22

Custom OS images on AWS

You can now configure your own AMIs for the AWS backend.

projects:
- name: main
  backends:
  - type: aws
    creds:
      type: default
    os_images:
      cpu:
        name: my-cpu-ami
        user: admin
      nvidia:
        name: my-nvidia-ami
        user: ubuntu

This can be used as an alternative way to bring your software or data to the AWS instance and mount it into your runs using Instance volumes.

See the AWS backend reference for details on configuring OS images. Support for custom OS images in other backends is coming in future releases.

What's Changed

Full Changelog: 0.18.21...0.18.22

Contributors

un-def, olgenn, and 3 other contributors
Assets 2
Loading

0.18.21

30 Oct 11:11
@r4victor r4victor
0.18.21
3858b8a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
0.18.21

Instance volumes

In addition to network volumes, dstack now allows to mount instance (host) filesystems inside the run container. As contents of the instance volume are specific to the instance where the run is executed, such volumes can be used in cases where data persistence is not critical, for example, as a cache:

type: task

commands:
  - pip install -r requirements.txt

volumes:
  # reuse pip cache between runs
  - /dstack-cache/pip:/root/.cache/pip

See the instance volumes documentation for more information.

Azure custom and private networks

dstack now supports configuring custom Azure networks, which was only possible on AWS and GCP before. In addition, you can now configure dstack to provision instances without public IPs on Azure to take advantage of private networks:

type: azure
  tenant_id: my_tenant_id
  subscription_id: my_subscription_id
  regions: [westeurope]
  public_ips: false
  vpc_ids:
    westeurope: test-networks-rg/test-network
  creds:
    type: default

Read more about Azure networking configuration in the docs.

Python 3.13 support for dstack package

The previous 0.18.20 release added support for Python 3.13 in run configurations. This release updates the dstack package itself so that it works under Python 3.13. The dstack package also drops Python 3.8 support that reached end of life. Note that python: 3.8 in run configurations is deprecated but still supported.

Multi-job UI

The control plain UI now displays detailed info on each job in the run, improving support for multi-node tasks and replicated services:

Screenshot 2024-10-30 at 15 09 03

What's Changed

New Contributors

Full Changelog: 0.18.20...0.18.21

Contributors

un-def, olgenn, and 6 other contributors
Assets 2
Loading

0.18.20

23 Oct 10:09
@r4victor r4victor
0.18.20
d8b11a3
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
0.18.20

Python 3.13 support

Following a recent Python 3.13 release on October 7, 2024, dstack now supports python: 3.13 in run configurations. python: 3.8 is still supported but deprecated.

Note: the dstack package itself does not yet work on Python 3.13 due to some limitations in dependencies. We're looking into supporting it as well.

Custom backend tags

You can now define custom tags that dstack will assign to all cloud resources it creates including instances and volumes. The tags are defined in the backend configuration:

type: aws
tags:
  company_department: finance
  company_project: dstack
  company_user: victor
creds:
  type: default

Custom tags are supported for AWS, Azure, and GCP.

Improved support of AWS private subnets

Previously, when configuring an AWS backend to use private subnets (public_ips: false), dstack would require a NAT Gateway. Now dstack supports more networking setups that provide outbound internet traffic including NAT Gateway, Transit Gateway, and VPC Peering Connection.

New required permissions

  • dstack now sets labels on GCP volumes which requires a compute.disks.setLabels permission.

Deprecations

  • python: 3.8 in run configurations is deprecated.

What's Changed

Full Changelog: 0.18.19...0.18.20

Contributors

un-def, olgenn, and 3 other contributors
Assets 2
Loading

0.18.19

17 Oct 07:25
@r4victor r4victor
0.18.19
a171ba6
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
0.18.19

This release contains CLI hotfixes for 0.18.18, including a fix for client backward compatibility and a fix for reported memory usage in dstack stats. It's recommended to update the CLI from 0.18.18 to 0.18.19. The server update from 0.18.18 is not necessary.

What's Changed

Full Changelog: 0.18.18...0.18.19

Contributors

un-def, Bihan, and 2 other contributors
Assets 2
Loading

0.18.18

16 Oct 15:04
@r4victor r4victor
0.18.18
10e587d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
0.18.18

Hardware metrics

The CLI introduces a new command, dstack stats, which displays real-time hardware metrics for runs, including CPU,
memory, and GPU usage per replica and job.

$ dstack stats hot-frog-1
 NAME        CPU  MEMORY           GPU                        
 hot-frog-1  2%   15307MB/49152MB  #0 22764MB/24576MB 0% Util

Use the -w option to view stats updating every few seconds in the loop.

You can also retrieve the metrics using the REST API.

Docker inside dstack

Run configurations now have a new optional privileged property (equivalent to the
--privileged Docker CLI flag).
When it is set to true, the run container gets extended privileges, making it possible to use Docker inside
dstack.

To use Docker and Docker Compose within dstack, set the image property
to dstackai/dind. Additionally, you must invoke start-dockerd as the first command to start the Docker daemon.

type: task
name: misc-task-dind

image: dstackai/dind
privileged: true

commands:
  - start-dockerd
  - docker compose up
Dev environment example 
type: dev-environment
name: vscode-dind

image: dstackai/dind
privileged: true
ide: vscode

init:
  - start-dockerd

See more examples in examples/misc/docker-compose.

Note

The privileged property is only supported by VM backends (all backends except runpod, vastai, and kubernetes).

What's changed

New contributors

Full changelog: 0.18.17...0.18.18

Contributors

mtaran, un-def, and 12 other contributors
Assets 2
Loading

0.18.17

09 Oct 10:20
@r4victor r4victor
0.18.17
8a2b9d1
Compare
Choose a tag to compare
0.18.17

On-prem AMD GPU support

dstack now supports SSH fleets with AMD GPUs. Hosts should be pre-installed with Docker and AMDGPU-DKMS kernel driver (e.g. via native package manager or AMDGPU installer).

Elastic Fabric Adapter support

dstack now automatically enables AWS EFA if it is supported by the instance type, no extra configuration needed. The following EFA-enabled instance types are supported: p5.48xlarge, p4d.24xlarge, g4dn.12xlarge, g4dn.16xlarge, g4dn.8xlarge, g4dn.metal, g5.12xlarge, g5.16xlarge, g5.24xlarge, g5.48xlarge, g5.8xlarge, g6.12xlarge, g6.16xlarge, g6.24xlarge, g6.48xlarge, g6.8xlarge, gr6.8xlarge.

Improved apply plan

Previously, dstack apply showed a plan only for run configurations. Now it shows a plan for all configuration types including fleets, volumes, and gateways. Here's a fleet plan showing configuration parameters and the offers that will be tried for provisioning:

✗ dstack apply -f .dstack/confs/fleet.yaml
 Project        main                           
 User           admin                          
 Configuration  .dstack/confs/fleet.yaml       
 Type           fleet                          
 Fleet type     cloud                          
 Nodes          2                              
 Placement      cluster                        
 Backends       aws                            
 Resources      2..xCPU, 8GB.., 100GB.. (disk) 
 Spot policy    on-demand                      

 #  BACKEND  REGION        INSTANCE   RESOURCES                   SPOT  PRICE    
 1  aws      eu-west-1     m5.large   2xCPU, 8GB, 100.0GB (disk)  no    $0.107   
 2  aws      eu-central-1  m5.large   2xCPU, 8GB, 100.0GB (disk)  no    $0.115   
 3  aws      eu-west-1     c5.xlarge  4xCPU, 8GB, 100.0GB (disk)  no    $0.192   
    ...                                                                          
 Shown 3 of 82 offers, $40.9447 max

Fleet my-cluster-fleet does not exist yet.
Create the fleet? [y/n]:

Volumes UI

Server administrators and regular users can now see volumes in the UI.

What's Changed

New Contributors

Full Changelog: 0.18.16...0.18.17

Contributors

un-def, olgenn, and 5 other contributors
Assets 2
Loading

0.18.16

30 Sep 10:29
@r4victor r4victor
0.18.16
fccc8dd
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
0.18.16

New versioning policy

Starting with this release, dstack adopts a new versioning policy to provide better server and client backward compatibility and improve the upgrading experience. dstack continues to follow semver versioning scheme ({major}.{minor}.{patch}) with the following principles:

  • The server backward compatibility is maintained across all minor and patch releases. The specific features can be removed but the removal is preceded with deprecation warnings for several minor releases. This means you can use older client versions with newer server versions.
  • The client backward compatibility is maintained across patch releases. A new minor release indicates that the release breaks client backward compatibility. This means you don't need to update the server when you update the client to a new patch release. Still, upgrading a client to a new minor version requires upgrading the server too.

Perviously, dstack never guaranteed client backward compatibility, so you had to always update the server when updating the client. The new versioning policy makes the client and server upgrading more flexible.

Note: The new policy only takes affect after both the clients and the server are upgraded to 0.18.16. The 0.18.15 server still won't work with newer clients.

dstack attach

The CLI gets a new dstack attach command that allows attaching to a run. It establishes the SSH tunnel, forwards ports, and streams run logs in real time:

 ✗ dstack attach silent-panther-1
Attached to run silent-panther-1 (replica=0 job=0)
Forwarded ports (local -> remote):
  - localhost:7860 -> 7860
To connect to the run via SSH, use `ssh silent-panther-1`.
Press Ctrl+C to detach...

This command is a replacement for dstack logs --attach with major improvements and bugfixes.

CloudWatch-related bugfixes

The releases includes several important bugfixes for CloudWatchLogStorage. We strongly recommend upgrading the dstack server if it's configured to store logs in CloudWatch.

Deprecations

  • dstack logs --attach is deprecated in favor of dstack attach and may be removed in the following minor releases.

What's Changed

Full Changelog: 0.18.15...0.18.16

Contributors

un-def, Bihan, and 2 other contributors
Assets 2
Loading