Skip to content

Releases: dstackai/dstack

0.18.28

26 Nov 11:32
@un-def un-def
0.18.28
de0ff48
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.28 Latest
Latest

CLI improvements

  • Added alias -R for --reuse with dstack apply
  • Shorten model URL output
  • dstack apply and dstack attach no longer rely on external tools such as ps and grep on Unix-like systems and powershell on Windows. With this change, it's now possible to use dstack CLI client in minimal environments such as Docker containers, including the official dstackai/dstack image

What's Changed

Full Changelog: 0.18.27...0.18.28

Contributors

un-def, jvstme, and peterschmidt85
Assets 2
Loading

0.18.27

22 Nov 09:42
@jvstme jvstme
0.18.27
d8b6ccb
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.27

UI/UX improvements

This release fixes a login issue in the control plane UI and introduces other UI/UX improvements.

What's Changed

Full Changelog: 0.18.26...0.18.27

Contributors

olgenn, jvstme, and peterschmidt85
Assets 2
Loading

0.18.26

20 Nov 16:02
@un-def un-def
0.18.26
b26d4ed
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.26

Git

Previously, when you called dstack init, Git credentials were reused between users of the same project and repository.

Starting with this release, to improve security, dstack no longer shares Git credentials across users.

Warning

If you submitted credentials earlier with dstack init, they will continue to work. However, it is recommended that each user call dstack init again to ensure they do not reuse credentials from other users.

Deleting legacy credentials

To ensure no credentials submitted earlier are shared across users, you can run the following SQL statements:

UPDATE repos SET creds = NULL;

UI

This update brings a few UI improvements:

  • Added Delete button to the Volumes page
  • Added Refresh button to all pages with lists: Runs, Models, Fleets, Volumes, Projects
  • Improved Code button on the model page

What's changed

  • Implement per-user repo creds storage by @un-def in #2004
  • [UI] Add Refresh button to all pages with lists by @olgenn in #2007
  • [UI] Include base URL and authentication token in the code snippets by @olgenn in #2006
  • [UI] The Code button improvements on the Model page by @olgenn in #2001
  • [UI] It's not possible to select and delete volumes by @olgenn in #2000
  • [UI] [Bug]: Services without model mapping are displayed in Models UI by @olgenn in #1993
  • Ensure sshd privsep dir in container is properly set up by @un-def in #2008
  • [Docs] Many minor improvements to docs and examples by @peterschmidt85 in #2013
  • [Docs] Services without a gateway by @jvstme in #2011
  • [Docs] Add deployment section with vLLM, TGI and NIM. Remove alignment handbook by @Bihan in #1990
  • [Docs] Updated Installation and Server deployment guides to include CloudFormation by @peterschmidt85
  • [Docs] Update services docs to reflect that gateway is now optional by @peterschmidt85 in #2005
  • [Examples] Add a CloudFormation template showing how to deploy dstack server to AWS by @peterschmidt85 in #1944
  • [Examples] Add Airflow example by @r4victor in #1991

Full changelog: 0.18.25...0.18.26

Contributors

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

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

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