sandbox: use args from sandboxer instead of os #30
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
Signed-off-by: Zhang Tianyang <burning9699@gmail.com>
Burning1020
force-pushed
the
get-rid-of-os-args
branch
from
060cbfd to
76c7af0
Compare
abel-von
approved these changes
Apr 18, 2024
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.
Flags of sandboxer working dir and listening address are now parsed from os, that is quite ugly.
They could be parsed by underlaying sandboxer themself and paased to
run.vmm-sandboxer --- | wasm-sandboxer -------> Parse flags from os ----> containerd_sandbox::run("xxx", listen, dir, sandboxer) | quark-sandboxer ---