OS Images
Every CVM on Phala Cloud runs on a dstack OS image. The image is the guest operating system: virtual firmware, a Linux kernel, an initramfs, and a read-only root filesystem. Phala Cloud lists every image it has published in the OS image registry.
What is an OS image hash?
It is one SHA-256 value that names an exact OS image. dstack computes it from the list of the image’s files and their own hashes, so changing any file changes the OS image hash. Each image release ships the same value in its digest.txt file, so you can rebuild the image and compare.
How is the hash checked when a CVM starts?
The CPU measures the firmware, the kernel, and the boot settings into the CVM’s attestation report. The KMS takes the image that has this hash, works out the measurements it should produce, and compares them with the report. It gives keys only when they match and the hash is on its allowlist.
What does "allowed by a KMS" mean?
A CVM gets its keys from a KMS each time it starts. The KMS gives keys only to a CVM whose OS image hash is on its allowlist. If the hash is not on the list, the KMS refuses, and the CVM cannot get its keys. The registry asks each KMS when you load the page. Results are cached for up to one minute. Read more about the KMS in KMS.
What does "Available on Phala Cloud" mean?
You can pick that image when you create or update a CVM today. Other images in the registry are retired, not released yet, or for testing. Phala Cloud no longer offers them, but a KMS may still allow them, so CVMs that already use them keep working after a restart.
How do I check the OS image of my CVM?
Copy the OS image hash from your CVM’s attestation report and paste it into Reference values. It tells you which image and dstack version the hash belongs to and which KMS allows it.