dstack-0.6.0
0x8409e2a24ea8325f3ea45d7c50622c952a8a4a961ffc139f5d9a81c4e47bd744Phala KMS 2026-11Not allowedEthereumNot allowedBaseNot alloweddstack 0.6.0 is the first release from the monorepo.
Upgrading from 0.5.x? Read the upgrade guide first: most apps only switch the guest image, but a few guest OS changes can stop an app from starting.
| Component | Release | Image |
|---|---|---|
| Guest OS | mkosi-os-v0.6.0 | os_image_hash: 8409e2a24ea8325f3ea45d7c50622c952a8a4a961ffc139f5d9a81c4e47bd744 |
| KMS | kms-v0.6.0 | ghcr.io/dstack-tee/dstack-kms:0.6.0 |
| Gateway | gateway-v0.6.0 | ghcr.io/dstack-tee/dstack-gateway:0.6.0 |
| Verifier | verifier-v0.6.0 | ghcr.io/dstack-tee/dstack-verifier:0.6.0 |
dstack.guest.v1, with domain-separated key
derivation, GPU evidence, and one attestation entry point on every platform.
The v0 API is frozen at v0.5.11 and keeps working unchangeddns-persist-01 (experimental)os_image_hash on chain
before deploying 0.6.0 images. The VMM now defaults qemu_hotplug_off to
true, which changes the ACPI tables and RTMRs of every CVM on its next
start, whatever its image; update any allowlist that pins MRs, or set it
back to false on hosts without GPUs (#1387)pre_launch_script runs under
set -euo pipefail; a GPU CVM must pass GPU attestation to boot unless
requirements.gpu_policy.attest_gpu is false; legacy iptables is gone;
environment variables arrive byte for byte instead of with \n escaped;
and an encrypted environment that cannot be decrypted stops the bootGetKey needs an asset migration
signed by the old key; see docs/guest-api-v1.md. v1 attestations and
v1-issued RA-TLS certificates need KMS and verifiers 0.5.9 or laterDstackClient now means DstackClientV1; name DstackClientV0
to stay on v0. Deep imports of the v0 modules gain a _v0 suffix, and the
Python v0 client emits a DeprecationWarningEmitEvent always fails; bind app data through
report_data instead. GetQuote answers on Intel TDX only; use Attest
elsewherenitro_enclave_key_release = true
(#1303), and the Nitro Enclave device_id is now sha256(PCR4), so
DstackApp contracts with allowAnyDevice = false must add the new value
(#1302). Root-key handover moves to the admin listener; turn off
core.onboard.public_key_handover once every node is upgraded (#1307)auth_token or htpasswd_file refuses to start. The VMM's [auth]
now guards the whole API and web UIcore.debug.insecure_skip_attestation is gone, and a gateway
without a guest agent no longer starts (#1148). A certificate configured in
[core.proxy] is ignored; install it with Admin.ImportCert (#1239)key_provider_id cannot boot its 0.5.x
image on a 0.6.0 VMM; move it to the 0.6.0 image with the host. Upgrade
netd together with the VMM, and before it on hosts running
bridge or macvtap VMs (#1145, #1217)ghcr.io/dstack-tee/<component>
(#1222). dstackup digest-pins its default KMS image, so fresh installs
register a different KMS app idFull changelog: CHANGELOG.md