Skip to main content

dstack 0.5.14

Available on Phala Cloud

Version 0.5.14Available on Phala Cloud

dstack-0.5.14

0x12f6dc37d20c3b75a3664da14ca255b78c66d6f356684008709ecf3026ac7685Phala KMS 2026-11AllowedEthereumAllowedBaseAllowed

dstack-dev-0.5.14dev

0x0dbfab4974393551939a7305eb452ad4e03af48b0ec6be60a3827737f58d7b76Phala KMS 2026-11AllowedEthereumNot allowedBaseNot allowed

dstack-nvidia-0.5.14GPU

0xd237ba2816f3b9ec944b1d8988b66f3ad5947dc61e47c69b1e17d5f9ce391dcdPhala KMS 2026-11AllowedEthereumAllowedBaseAllowed

dstack-nvidia-dev-0.5.14devGPU

0x7ff4691f42f3c7ca01b2e334f2bce98a85486bf0a8306a6c3ea5287c51571c7ePhala KMS 2026-11AllowedEthereumNot allowedBaseNot allowed

Changelog

dstack

Dstack-TEE/dstack@v0.5.14

Maintenance release for the 0.5 line. It adds the guest side of the 0.6.4 KMS key epoch migration, so 0.5 guests keep booting after the KMS rotates its root key epoch or an app's key epoch. It ships in the meta-dstack v0.5.14 guest OS image. KMS, Gateway and Verifier are unchanged, so there are no new component releases.

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

Why upgrade before a rotation

A 0.6.4 KMS answers a key request that names no epoch with the keys of the current epochs. After a rotation, a 0.5.13 or older guest gets keys that open neither its data disk nor its encrypted env, and fails to boot. Upgrade every 0.5 guest to 0.5.14 before activating a new root epoch or advancing an app epoch.

Guest setup (dstack-util)

  • Data disk: when the current key does not unlock the disk, the guest fetches the key of the epochs recorded on the disk from the KMS and re-keys the LUKS2 keyslot to the current epochs. Each step is crash-safe, and the disk records the new epochs in a dstack-kms LUKS token. A disk that was never rotated is left untouched (#1574).
  • Encrypted env: the guest accepts SealedEnv (HPKE) envelopes. If the current key cannot open a legacy encrypted env, it uses the keys of older epochs. A migrated env is re-sealed to the current epochs and handed to the VMM with UpdateSealedEnv, which also closes the env update window before applications start (#1574).
  • Historical key requests: these pin the KMS root CA established at boot and do not extend RTMR3 (#1574).
  • LUKS2 header validation: the 0.6.4 parser replaces the luks2 crate check. It keeps every existing check, additionally requires the two header copies to agree, and accepts the single dstack epoch token and, during a migration, a second keyslot (#1574).

Operational notes

  • Persisting the migrated env needs dstack-vmm 0.6.4. The 0.5.14 image declares sealed_env support so the VMM can store it. Under an older VMM the guest repeats the env migration on every boot.
  • Keep old-epoch policy until migration finishes. Do not revoke the policy of old epochs until every VM has migrated its disk and stored env.
  • Downgrades: a migrated disk or env cannot be opened by an older image.
  • App GetKey results change after a rotation. They are derived from the current epochs, and 0.5.14 does not expose historical application keys. Applications that need old keys should upgrade to 0.6.4, which serves them over the v1 API.

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

Guest OS

Dstack-TEE/meta-dstack@v0.5.14

Maintenance release of the 0.5 guest OS. It adds the guest side of the dstack 0.6.4 KMS key epoch migration, so CVMs keep their data disk and encrypted env after the KMS rotates its root key epoch or an app's key epoch.

We recommend upgrading to dstack 0.6.4. If you stay on 0.5, upgrade every 0.5 guest to this image before activating a new root epoch or advancing an app epoch. A 0.5.13 or older guest cannot open its disk or env after a rotation. 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.1412f6dc37d20c3b75a3664da14ca255b78c66d6f356684008709ecf3026ac7685
dstack-dev-0.5.140dbfab4974393551939a7305eb452ad4e03af48b0ec6be60a3827737f58d7b76
dstack-nvidia-0.5.14d237ba2816f3b9ec944b1d8988b66f3ad5947dc61e47c69b1e17d5f9ce391dcd
dstack-nvidia-dev-0.5.147ff4691f42f3c7ca01b2e334f2bce98a85486bf0a8306a6c3ea5287c51571c7e

metadata.json keeps ovmf_variant: pre202505 and kernel_header_normalized: true, and adds sealed_env: true.

meta-dstack changes (v0.5.13 → v0.5.14)

  • metadata.json declares sealed_env: true. A dstack-vmm 0.6.4 then accepts SealedEnv for these images, and stores the env the guest re-seals to the current epochs after a rotation (#85).
  • Bump version to 0.5.14; the dstack submodule now points to the 0.5.14 release commit.

dstack submodule changes (v0.5.13 → v0.5.14)

  • Data disk: when the current KMS key does not unlock it, the guest re-keys the LUKS2 keyslot from the recorded epochs to the current ones with crash-safe steps. A disk that was never rotated is left untouched.
  • Encrypted env: the guest opens SealedEnv envelopes. It opens a legacy env with older epochs' keys when needed, and hands the re-sealed env to the VMM.

See the dstack v0.5.14 release notes for details and operational notes.

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