vmm: disallow ISO rootfs for image versions >= 0.5.0#663
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
dstack-utilsetup path no longer accepts or validates a rootfs hash, which combined with the VMM still permitting.isorootfs attachments allows a host to substitute an unverified rootfs and break the chain-of-trust.Description
vmm/src/app/qemu.rsthat readsimg_ver = self.image.info.version_tuple()andbail!s when the rootfs extension is"iso"for images with version>= (0, 5, 0)so modern images must use verity-backed rootfs..verityhandling unchanged and continue allowing.isofor older/legacy image versions to maintain backward compatibility.Testing
cargo check -p dstack-vmmwhich completed successfully.Codex Task