Available on Phala Cloud
0xfeff3645893ad910d4f0e06d8f553cf80a7c9fede2ce0698fa63116283260366dstack 0.6.4 introduces KMS root and application key epochs, SealedEnv, and TEE platform allowlists in the KMS contracts. The contracts, auth backend, KMS and guests must be upgraded in a fixed order — see Upgrade notes.
| Component | Release | Image |
|---|---|---|
| Guest OS | mkosi-os-v0.6.4 | os_image_hash: feff3645893ad910d4f0e06d8f553cf80a7c9fede2ce0698fa63116283260366 |
| KMS | kms-v0.6.4 | ghcr.io/dstack-tee/dstack-kms:0.6.4@sha256:3c8746c4a638e0a96e69f19d8830f9c560466ee26e733a5c6c81e6ca2e213784 |
| KMS auth-eth | kms-auth-eth-v0.6.4 | ghcr.io/dstack-tee/dstack-kms-auth-eth:0.6.4@sha256:84f98c0bb4297c608fcea299e93661e97f80289d03771bd6d490968555921090 |
| Gateway | gateway-v0.6.4 | ghcr.io/dstack-tee/dstack-gateway:0.6.4@sha256:786ebff62700bd5d7e02a340d7f00dcefc8378fb65aed9078ab61e449ab08357 |
| Verifier | verifier-v0.6.4 | ghcr.io/dstack-tee/dstack-verifier:0.6.4@sha256:a55a5d8d409a8b8e99156b17abf31c54a3fe268e7ad7c4241047b9f008a90ccb |
setAllowAnyTeeVariant,
setAllowedTeeVariants); approvals are per epoch.key_provider: sev-snp lets a KMS CVM on an AMD host keep its
disk and root keys across restarts without SGX.auth-eth-bun is renamed auth-eth (ghcr.io/dstack-tee/dstack-kms-auth-eth);
the Node server, auth-simple and auth-mock are removed.DstackKms and DstackApp proxies
(script/Upgrade.s.sol), point setAppImplementation at the new
DstackApp, and register the existing roots as root epoch 0
(registerRootEpoch). Several contract functions are removed or replaced by
per-epoch forms; see the KMS release notes.auth-eth; custom webhook backends must
serve GET /app/:appId. auth-eth now reads policy at the finalized block.core.onboard.public_key_handover = true.
Upgrade every KMS before deploying 0.6.4 guests.os_image_hash on chain, then deploy.Keep root and app epochs at 0 until every KMS and guest runs 0.6.4.
Full changelog: CHANGELOG.md