-
Notifications
You must be signed in to change notification settings - Fork 2.5k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
timeout for podman run #24968
Comments
I set these syscall, is there any syscall affect podman? "syscalls": [
{
"names": [
"bind",
"close",
"connect",
"setsockopt",
"fcntl",
"_exit",
"exit_group",
"getpeername"
],
"action": "SCMP_ACT_NOTIFY" |
yes, close surely affect the OCI runtime, as well as exit. Does it work if you don't override the seccomp profile? |
yes, it works when I don't override the seccomp profile or delete all syscalls that I set. |
is there any other syscall that affect OCI below? "bind",
"close",
"connect",
"setsockopt",
"fcntl",
"_exit",
"exit_group",
"getpeername" |
that's is runtime specific. crun might use less syscalls than runc |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
podman run -it --rm --security-opt seccomp=$HOME/seccomp.json --runtime=runc iperf3 -s
when I execute this command, I found that it would always be stuck here
Maybe it’s because my user-mode decision program is not started?
Is there a way to make the decision program start after podman creates the container process?
The text was updated successfully, but these errors were encountered: