Add container-snap #137
Draft
Add container-snap #137
Conversation
This file contains 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.
This is a draft PR to add support for container-snap, a highly experimental deployment tool of OCI images (this is comparable to #128, but uses a different mechanism).
The current implementation "works" to reboot into a snapshot based on a container image, but it's very far from being pretty or anywhere close to being end user usable.
Existing shortcomings:
getListdoesn't appear to work properly and is not easy to pull off, ascontainer-snapdoesn't support all the info that snapper doesgetDefaultandgetCurrentcurrently return the same thing (I am unsure what the difference between them is)inProgressis not really doing anything useful atm, ascontainer-snaphas no implementation of "in progress" (yet).