We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Looking at the runc seccomp code, it seems that our flag handling (added by #3390) is broken.
This happens because since #2750 runc no longer uses libseccomp-golang's filter.Load(), but rather implements its own loader.
filter.Load()
This means, that whatever flags we set using libseccomp-golang's filter.SetXXX() are not being used.
filter.SetXXX()
Instead, patchebpf.filterFlags is used to query flags from the filter and set them. Alas, it only supports a subset of currently supported flags.
patchebpf.filterFlags
The text was updated successfully, but these errors were encountered:
cc @alban
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Looking at the runc seccomp code, it seems that our flag handling (added by #3390) is broken.
This happens because since #2750 runc no longer uses libseccomp-golang's
filter.Load(), but rather implements its own loader.This means, that whatever flags we set using libseccomp-golang's
filter.SetXXX()are not being used.Instead,
patchebpf.filterFlagsis used to query flags from the filter and set them. Alas, it only supports a subset of currently supported flags.The text was updated successfully, but these errors were encountered: