-
Notifications
You must be signed in to change notification settings - Fork 1.2k
runtime-rs: add seccomp support for cloud hypervisor and firecracker #11536
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
# Disable the 'seccomp' feature from Cloud Hypervisor or firecracker, default false | ||
# disable_seccomp = true | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I saw you added a test condition for seccomp in fc, but why is it absent in clh?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This has been implemented in Cloud Hypervisor.
let disable_seccomp = cfg.security_info.disable_seccomp; |
kata-containers/src/runtime-rs/crates/hypervisor/src/ch/inner_hypervisor.rs
Lines 358 to 360 in 294b2c1
if disable_seccomp { | |
cmd.args(["--seccomp", "false"]); | |
} |
The seccomp feature for Cloud Hypervisor and Firecracker is enabled by default. This commit introduces an option to disable seccomp for both and updates the built-in configuration.toml file accordingly. Fixes: kata-containers#11535 Signed-off-by: wangxinge <wangxinge@bupt.edu.cn>
38239f0
to
f3a669e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm, thanks!
The seccomp feature for Cloud Hypervisor and Firecracker is enabled by default. This commit introduces an option to disable seccomp for both and updates the built-in configuration.toml file accordingly.
Fixes: #11535