0.18.14

Multi-replica server deployment

Previously, the dstack server only supported deploying a single instance (replica). However, with 0.18.14, you can now deploy multiple replicas, enabling high availability and zero-downtime updates

Note

Multi-replica server deployment requires using Postgres instead of the default SQLite. To configure Postgres, set the DSTACK_DATABASE_URL environment variable.

Make sure to update to version 0.18.14 before configuring multiple replicas.

Major bug-fixes

• [Bugfix] dstack init --git-identity doesn't accept backslashes in path on Windows by @un-def in #1686
• [Bugfix] Use -tmpfs /dev/shm:rw,nosuid,nodev,exec,size=X instead of --shm-size=X @un-def in #1690
• [Bugfix] dstack-shim is not updated when fleet is recreated by @un-def in #1698

Other

• [Bugfix] Fix SSHAttach.reuse_ports_lock() when no grep matches by @un-def in #1700
• [Bugfix] Fix logger exception on instance provisioning timeout by @un-def in #1697
• [Internal] Add JobProvisioningData.base_backend by @r4victor in #1682
• [Internal] Add Run.error by @r4victor in #1684
• [Internal] Return server_version in /api/server/get_info by @r4victor in #1685
• [Internal] Allow gateway to connect to replicated server by @jvstme in #1688
• [Internal] Adjust gateway management for multiple server replicas by @r4victor in #1691
• [Internal] Skip gateway update if gateway was updated recently by @r4victor in #1695
• [Internal] Remove redundant logger.error by @r4victor in #1702

Full changelog: 0.18.13...0.18.14