This bug has been verified on podman-4.2.0-2.module+el8.7.0+16894+3f997fa3.
[root@test-8-7-0-bz2130236 ~]# podman inspect foo | grep -iA2 args
WARN[0000] Error unmarshalling container dda2a8b2d269180250e32220f3ce645c15f271478b7d6f96846cd2aab40d6c43 config: readObjectStart: expect { or n, but found , error found in #0 byte of ...||..., bigger context ...||...
"Args": [
"infinity"
],
[root@test-8-7-0-bz2130236 ~]# cat /etc/redhat-release
Red Hat Enterprise Linux release 8.7 (Ootpa)
[root@test-8-7-0-bz2130236 ~]# rpm -q podman runc systemd kernel
podman-4.2.0-2.module+el8.7.0+16894+3f997fa3.x86_64
runc-1.1.4-1.module+el8.7.0+16894+3f997fa3.x86_64
systemd-239-68.el8.x86_64
kernel-4.18.0-425.3.1.el8.x86_64
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: 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:7822