Repository navigation
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
| Image | os_image_hash |
|---|---|
dstack-0.5.14 |
12f6dc37d20c3b75a3664da14ca255b78c66d6f356684008709ecf3026ac7685 |
dstack-dev-0.5.14 |
0dbfab4974393551939a7305eb452ad4e03af48b0ec6be60a3827737f58d7b76 |
dstack-nvidia-0.5.14 |
d237ba2816f3b9ec944b1d8988b66f3ad5947dc61e47c69b1e17d5f9ce391dcd |
dstack-nvidia-dev-0.5.14 |
7ff4691f42f3c7ca01b2e334f2bce98a85486bf0a8306a6c3ea5287c51571c7e |
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.jsondeclaressealed_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
dstacksubmodule 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: v0.5.13...v0.5.14