-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
systemd: fix NOTIFY_SOCKET with patched runc #1798
systemd: fix NOTIFY_SOCKET with patched runc #1798
Conversation
871754f
to
347ae34
Compare
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 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 |
LGTM |
LGTM |
bot, retest this please |
Change LGTM, all kinds of test unhappiness though. |
deed469
to
9e6fa9b
Compare
I think SELinux will block the tests from running correctly until we get the updates container-selinux package. |
8330d0f
to
6ae25fd
Compare
bot, retest this please |
84b422b
to
712e0d9
Compare
19ae69a
to
d4d1a0d
Compare
do not make any assumption on the path inside of the container. Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
with opencontainers/runc#1807 we moved the systemd notify initialization from "create" to "start", so that the OCI runtime doesn't hang while waiting on reading from the notify socket. This means we also need to set the correct NOTIFY_SOCKET when start'ing the container. Closes: containers#746 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
d766fd5
to
22e923b
Compare
the NOTIFY_SOCKET test blocks without a fixed runc, so I've enabled it only on Fedora/CentOS/RHEL |
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
22e923b
to
180d0c6
Compare
This LGTM. Will merge once tests green. |
tests are green |
/lgtm |
I'm confused, why did this close #746? |
with opencontainers/runc#1807 we moved the systemd notify initialization from "create" to "start", so that the OCI runtime doesn't hang while waiting on reading from the notify socket. This means we also need to set the correct NOTIFY_SOCKET when start'ing the container.
Closes: #746