Repository navigation
feat(image): declare SealedEnv support in metadata.json - #85
Merged
Merged
Conversation
A 0.6.4 VMM stores the env a guest re-seals to the current KMS key epochs only for an image that declares sealed_env. The guest support comes with Dstack-TEE/dstack#1574; bump the dstack submodule to a commit including it before releasing an image with this change. Signed-off-by: Kevin Wang <wy721@qq.com>
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.
Declares
"sealed_env": trueso a 0.6.4 VMM accepts SealedEnv for 0.5.x images and stores the env the guest re-seals after a KMS key epoch rotation.Depends on Dstack-TEE/dstack#1574: merge it and bump the
dstacksubmodule before releasing an image with this change.