-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[3.2.3-rhel] seccomp: propagate defaultErrnoRet #11039
[3.2.3-rhel] seccomp: propagate defaultErrnoRet #11039
Conversation
This fixes the issue of not propagating defaultErrnoRet from system's seccomp.json to container's config.json, which can result in redundant seccomp rules and inability to start a container when using some runtimes (notably runc up to and including 1.0.1). The fix is to vendor in containers/common with the fixed pkg/seccomp which no longer ignores defaultErrnoRet. Brought to you by: go get github.com/containers/[email protected] make vendor Signed-off-by: Kir Kolyshkin <[email protected]>
Do we have a new-enough c/common in 8.4.0.2 to require this? If so, I think
we definitely need a BZ spun up to get this landed.
…On Sun, Jul 25, 2021 at 7:01 AM openshift-ci[bot] ***@***.***> wrote:
[APPROVALNOTIFIER] This PR is *NOT APPROVED*
This pull-request has been approved by: *kolyshkin
<#11039#>*
To complete the pull request process
<https://git.k8s.io/community/contributors/guide/owners.md#the-code-review-process>,
please assign *jwhonce* after the PR has been reviewed.
You can assign the PR to them by writing /assign @jwhonce in a comment
when ready.
The full list of commands accepted by this bot can be found here
<https://go.k8s.io/bot-commands?repo=containers%2Fpodman>.
Needs approval from an approver in each of these files:
- *OWNERS
<https://github.com/containers/podman/blob/v3.2.3-rhel/OWNERS>*
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#11039 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB3AOCATKS3ORIAZ3MZ77KTTZPVJDANCNFSM5A6NVI6A>
.
|
I assume we don't. As long as the vendored version is used for building podman in rhel (which I believe is how things are), we do not care about what version of containers-common rpm is installed. |
Yes, we need a BZ to merge any PR into the -rhel branch (also to start rebuilding packages). @kolyshkin, would you open one? /hold |
Done, please see bugzilla.redhat.com/1987049 Description updated. |
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
Let's wait for an ACK in the BZ before merge. Thank you, Kir!
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kolyshkin, rhatdan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel |
(same as #11033 but for v3.2.3-rhel branch)
This fixes the issue of not propagating defaultErrnoRet from
system's seccomp.json to container's config.json, which can
result in redundant seccomp rules and inability to start a container
when using some runtimes (notably runc up to and including 1.0.1).
The fix is to vendor in containers/common with the fixed pkg/seccomp
which no longer ignores defaultErrnoRet.
Fixes: #11031
Fixes: bugzilla.redhat.com/1987049
Proposed changelog entry