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: podmanAssignee: Jindrich Novy <jnovy>
Status: CLOSED ERRATA QA Contact: Edward Shen <weshen>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 8.5CC: bbaude, dornelas, dwalsh, dwojewod, gscrivan, jhonce, jligon, jnovy, lsm5, mheon, pthomas, tsweeney, umohnani, vrothber, ypu
Target Milestone: rcKeywords: 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
Jhon, Valentin and Giuseppe any thouhgts on why this would happen, or is this a red herring?

I can't imagine this is much of a difference which would bring down the container started by the service.  As long as the service is moved out of the services cgroup.

Could someone try to verify if they can get this to happen.

Comment 5 Daniel Walsh 2022-03-02 18:06:27 UTC
Jon any idea what is going on here?

Comment 6 Jhon Honce 2022-03-16 22:39:11 UTC
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.

Comment 16 Daniel Walsh 2022-06-14 16:45:59 UTC
Is this different when you are using a unix domain socket, or does it break there as well?

Comment 17 Giuseppe Scrivano 2022-06-14 19:56:32 UTC
I do not see any difference when I use a UNIX domain socket

Comment 18 Daniel Walsh 2022-06-14 19:58:15 UTC
Ok, to fix this we would want to move the conmons out to their own cgroup correct?

Comment 19 Giuseppe Scrivano 2022-06-15 09:07:15 UTC
opened a PR upstream: https://github.com/containers/podman/pull/14596

Comment 20 Tom Sweeney 2022-06-28 20:21:37 UTC
As the PR is merged, I'm assigning this @jnovy for any further BZ/packaging needs

Comment 29 errata-xmlrpc 2022-11-08 09:14:55 UTC
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

Comment 30 Red Hat Bugzilla 2023-09-18 04:31:46 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days