Skip to content

Conversation

was-saw
Copy link
Contributor

@was-saw was-saw commented Jul 8, 2025

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

Comment on lines +197 to +200
# Disable the 'seccomp' feature from Cloud Hypervisor or firecracker, default false
# disable_seccomp = true

Copy link
Member

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?

Copy link
Contributor Author

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;

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>
Copy link
Member

@justxuewei justxuewei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm, thanks!

@justxuewei justxuewei merged commit 479cce8 into kata-containers:main Aug 14, 2025
507 of 539 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

runtime-rs: add seccomp support for cloud hypervisor and firecracker
3 participants