Bug 2052697
Summary: | Inconsistency in how the podman service behaves depending on whether it is providing API via UNIX or TCP socket. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Matt Mezynski <mmezynsk> |
Component: | podman | Assignee: | Jindrich Novy <jnovy> |
Status: | CLOSED ERRATA | QA Contact: | Edward Shen <weshen> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 8.5 | CC: | bbaude, dornelas, dwalsh, dwojewod, gscrivan, jhonce, jligon, jnovy, lsm5, mheon, pthomas, tsweeney, umohnani, vrothber, ypu |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | podman-4.2.0-1.el8 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-11-08 09:14:55 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Comment 2
Daniel Walsh
2022-02-10 21:54:28 UTC
Jon any idea what is going on here? The exit code handling is addressed in https://github.com/containers/podman/pull/13450 I was unable to reproduce the problem with the current podman code. I introduced systemd_activate_test.go to verify container state when `systemctl stop podman.service` is used. Is this different when you are using a unix domain socket, or does it break there as well? I do not see any difference when I use a UNIX domain socket Ok, to fix this we would want to move the conmons out to their own cgroup correct? opened a PR upstream: https://github.com/containers/podman/pull/14596 As the PR is merged, I'm assigning this @jnovy for any further BZ/packaging needs Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: container-tools:rhel8 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:7457 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |