Repository navigation
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
| Image | os_image_hash |
|---|---|
dstack-0.5.15 |
4597735f1a38ad8ec9f781356b88737fc052062deb7c9aaa4be89bf1b35643ca |
dstack-dev-0.5.15 |
432b8a1e82ec8a90b3d30bb201e5d20a8bc5c05b69f1d8ba13687232dda5aebd |
dstack-nvidia-0.5.15 |
3bb7d262416f47db06855d7b7cf7d380538747206014b3c0adcddfef9b7c4ef2 |
dstack-nvidia-dev-0.5.15 |
8ca5a74519d2229acf7d5439cd9d5ca08e8eb89f41060e1f04ef8c8a8e0c7894 |
Changes (v0.5.14 → v0.5.15)
- dstack submodule: the guest presents the launch ticket from its sys-config to the KMS in
GetAppKeyandSignCert; the ticket is never put invm_config(Dstack-TEE/dstack#1579). - Bump version to 0.5.15; the
dstacksubmodule now points to the 0.5.15 release commit.
See the dstack v0.5.15 release notes for the requirements.
Full commit log: v0.5.14...v0.5.15