Skip to main content

dstack 0.5.15

Version 0.5.15

dstack-0.5.15

0x4597735f1a38ad8ec9f781356b88737fc052062deb7c9aaa4be89bf1b35643caPhala KMS 2026-11AllowedEthereumNot allowedBaseNot allowed

dstack-dev-0.5.15dev

0x432b8a1e82ec8a90b3d30bb201e5d20a8bc5c05b69f1d8ba13687232dda5aebdPhala KMS 2026-11AllowedEthereumNot allowedBaseNot allowed

dstack-nvidia-0.5.15GPU

0x3bb7d262416f47db06855d7b7cf7d380538747206014b3c0adcddfef9b7c4ef2Phala KMS 2026-11AllowedEthereumNot allowedBaseNot allowed

dstack-nvidia-dev-0.5.15devGPU

0x8ca5a74519d2229acf7d5439cd9d5ca08e8eb89f41060e1f04ef8c8a8e0c7894Phala KMS 2026-11AllowedEthereumNot allowedBaseNot allowed

Changelog

dstack

Dstack-TEE/dstack@v0.5.15

Maintenance release for the 0.5 line. It adds the guest side of the KMS-enforced launch tickets of dstack 0.6.5 (#1577), so a 0.5 guest can boot an app whose contract requires a launch ticket. It ships in the meta-dstack v0.5.15 guest OS image. KMS, Gateway and Verifier are unchanged, so there are no new component releases.

We recommend upgrading to dstack 0.6.5. The 0.5 line receives fixes only.

Guest changes

  • Launch ticket: the guest reads the ticket the VMM writes to its sys-config and presents it to the KMS in GetAppKey (dstack-util) and SignCert (dstack-util and the guest agent). The ticket is never put in vm_config, which attestations embed (#1579).

Requirements

  • Launch tickets need dstack-vmm, dstack-kms, the auth backend (auth-eth or dstack-auth) and the DstackKms/DstackApp contracts at 0.6.5 or later. The VMM stores the ticket and passes it to the guest, the KMS forwards its hash, and the contract checks it. See launch tickets.
  • Without a ticket requirement nothing changes. A 0.5.15 guest boots as 0.5.14 did; a KMS older than 0.6.5 ignores the new request field.
  • Upgrade the guests before requiring a ticket. A 0.5.14 or older guest never sends the ticket, so once an app requires one, the KMS refuses it with Invalid launch ticket: no launch ticket was presented.

Guest OS

Dstack-TEE/meta-dstack@v0.5.15

Maintenance release of the 0.5 guest OS. It adds the guest side of the KMS-enforced launch tickets of dstack 0.6.5, so a CVM on this image can boot an app whose contract requires a launch ticket.

We recommend upgrading to dstack 0.6.5. Launch tickets need dstack-vmm, dstack-kms, the auth backend and the contracts at 0.6.5 or later. Without a ticket requirement this image behaves as 0.5.14. The OS image hash changes, so the new os_image_hash must be whitelisted in your KMS / DstackKms contract before CVMs can boot with it.

OS image hashes

Imageos_image_hash
dstack-0.5.154597735f1a38ad8ec9f781356b88737fc052062deb7c9aaa4be89bf1b35643ca
dstack-dev-0.5.15432b8a1e82ec8a90b3d30bb201e5d20a8bc5c05b69f1d8ba13687232dda5aebd
dstack-nvidia-0.5.153bb7d262416f47db06855d7b7cf7d380538747206014b3c0adcddfef9b7c4ef2
dstack-nvidia-dev-0.5.158ca5a74519d2229acf7d5439cd9d5ca08e8eb89f41060e1f04ef8c8a8e0c7894

Changes (v0.5.14 → v0.5.15)

  • dstack submodule: the guest presents the launch ticket from its sys-config to the KMS in GetAppKey and SignCert; the ticket is never put in vm_config (Dstack-TEE/dstack#1579).
  • Bump version to 0.5.15; the dstack submodule now points to the 0.5.15 release commit.

See the dstack v0.5.15 release notes for the requirements.

Full commit log: https://github.com/Dstack-TEE/meta-dstack/compare/v0.5.14...v0.5.15