Setting to Post and assigning to @jnovy . The fix from the cloned BZ in RHEL 8.7.0.ZeroDay will apply here too.
@ypu and Jindrich, can I get a QA and Dev ack please?
This bug has been verified on podman-4.2.0-5.el9_1 with runc-1.1.4-1.el9.
[root@test-9-1-0-bz2124716 ~]# podman inspect foo | grep -iA2 args
WARN[0000] Error unmarshalling container 44d38934fc16024dc11f67ffdd82ba2a6d0fbe91acd9463650fcb87ce5297c52 config: readObjectStart: expect { or n, but found , error found in #0 byte of ...||..., bigger context ...||...
"Args": [
"infinity"
],
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 (Low: podman 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:8431