v0.5.12

Security maintenance release of the 0.5 guest OS. It contains guest-side fixes backported from dstack 0.6 and nothing that changes measurement semantics (OVMF, kernel command line and RTMR layout are as in v0.5.11).

We recommend upgrading to dstack 0.6.1. If you stay on 0.5, upgrade to this image. 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.12	8db40cb23008d6213668b5816702d100b37b859a8a5bfd18d938ae3a1b3715bd
dstack-dev-0.5.12	e866e987221db357129ebc3f066b6706ef955889ea95e5510acbdf3d3055186b
dstack-nvidia-0.5.12	91fd5d69ccee3e5ea4f2aeb8c9b632c4358c4ecfc29ba1aa6fb1e402af209829
dstack-nvidia-dev-0.5.12	e0c9312d9a2a7cdc54fdd86264474f502a97282b464b6cdba4544b1e8a211734

metadata.json keeps ovmf_variant: pre202505.

meta-dstack changes (v0.5.11 → v0.5.12)

• Initramfs mounts /proc and /sys nosuid,nodev,noexec, /dev nosuid, and /run 0755; dm-verity is opened with --panic-on-corruption (backport of Dstack-TEE/dstack#1274). /etc/fstab now lists /proc with the same options, so systemd does not clear them after boot.
• NVIDIA container runtime logs at info instead of debug (backport of Dstack-TEE/dstack#1329).
• Bump version to 0.5.12; the dstack submodule now points to the 0.5.12 release commit.

dstack submodule changes (v0.5.11 → v0.5.12)

Guest agent and guest setup security fixes: logs-route container-name validation, quote calls off the async executor and cached Info, GetTlsKey validity bounds, KMS kms:rpc cert pinning, systemd env-file escaping, owner-only secret files, LUKS keyslot bounds, bounded host-share copy and nosuid,nodev,noexec host-share mount, remove-orphans with compose include:, and app-compose.service dependencies. See dstack v0.5.12 release notes.

Full commit log: v0.5.11...v0.5.12