Release 0.18.15 · dstackai/dstack

Cluster placement groups

Instances of AWS cluster fleets are now provisioned into cluster placement groups for better connectivity. For example, when you create this fleet:

type: fleet
name: my-cluster-fleet
nodes: 4
placement: cluster
backends: [aws]

dstack will automatically create a cluster placement group and use it to provision the instances.

All available Nvidia driver capabilities are now requested by default, which makes it possible to run GPU workloads requiring OpenGL/Vulkan/RT/Video Codec SDK libraries. (#1714)
Automatic container cleanup. Previously, when the run completed, either successfully or due to an error, its container was not deleted, which led to ever-increasing storage consumption. Now, only the last stopped container is preserved and is available until the next run is completed. (#1706)

Fixed a bug where under some conditions logs wouldn't be uploaded to CloudWatch Logs due to size limits. (#1712)
Fixed a bug that prevented running services on on-prem instances. (#1716)

Fix cli connection issue with TPU by @Bihan in #1705
Rename --default to --yes and no-default to --no in dstack config and dstack server by @peterschmidt85 in #1709
[CI] Fix shim/runner release versions by @un-def in #1704
Document run diagnostic logs by @r4victor in #1710
[shim] Add old container cleanup routine by @un-def in #1706
Write events to CloudWatch in batches by @un-def in #1712
[shim] Request all Nvidia driver capabilities by @un-def in #1714
Added showing dstack version on the UI by @olgenn in #1717
Add missing project SSH key to on-prem instances by @un-def in #1716
Simplify handling missing GatewayConfiguration by @jvstme in #1724
[shim] Fix container logs processing by @un-def in #1721
Support AWS placement groups for cluster fleets by @r4victor in #1725

Full Changelog: 0.18.14...0.18.15