Backport PR https://github.com/containers/podman/pull/15982
Merged
Assigning to @jnovy for any further BZ or packaging needs.
This bug has been verified on podman-4.1.1-7.module+el8.6.0+16889+9f154fa9 with netavark network backend. [root@test-8-6-0-bz2130237 ~]# podman inspect foo | grep -iA2 args WARN[0000] Error unmarshalling container 9afb33215d1e46cd37aba0940d276278c1a4d520cffe7fb5f93fea9412ef3db5 config: readObjectStart: expect { or n, but found , error found in #0 byte of ...||..., bigger context ...||... "Args": [ "infinity" ], [root@test-8-6-0-bz2126697 ~]# cat /etc/redhat-release Red Hat Enterprise Linux release 8.6 (Ootpa) [root@test-8-6-0-bz2126697 ~]# grep network_backend /usr/share/containers/containers.conf #network_backend = "" network_backend = "netavark" [root@test-8-6-0-bz2126697 ~]# rpm -q podman runc netavark systemd kernel podman-4.1.1-7.module+el8.6.0+16889+9f154fa9.x86_64 runc-1.1.3-2.module+el8.6.0+16771+28dfca77.x86_64 netavark-1.0.1-35.module+el8.6.0+15917+093ca6f8.x86_64 systemd-239-58.el8.x86_64 kernel-4.18.0-372.9.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 (container-tools:rhel8 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/RHBA-2022:7127