Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Always use our own seccomp policy as a default. #926

Merged
merged 1 commit into from
Oct 2, 2024
Merged

Always use our own seccomp policy as a default. #926

merged 1 commit into from
Oct 2, 2024

Commits on Oct 2, 2024

  1. Always use our own seccomp policy as a default. 

    As per Etienne Perot's comment on #908:

> Then it seems to me like it would be easy to simply apply this seccomp
profile under all container runtimes (since there's no reason why the
same image and the same command-line would call different syscalls under
different container runtimes).
    @almet
    almet committed Oct 2, 2024
    Configuration menu
    Copy the full SHA
    3e434d0 View commit details
    Browse the repository at this point in the history