
OPERATIONAL DEFECT DATABASE
...

...
What were you trying to do that didn't work? As root less user executing the below command which is resulting to error. podman run -it -m 512M registry.redhat.io/ubi8/ubi /bin/bash Resource limits are not supported and ignored on cgroups V1 rootless systems Error: container create failed (no logs from conmon): conmon bytes "": readObjectStart: expect { or n, but found , error found in #0 byte of ...||..., bigger context ...||... Please provide the package NVR for which bug is seen: podman-4.4.1-12.module+el8.8.0+18735+a32c1292.x86_64 podman-4.6.1-4.module+el8.9.0+20326+387084d0.x86_64 RHEL 8.8 cgroupVersion: v1 How reproducible: error appears while executing below command as root-less user podman run -it -m 512M registry.redhat.io/ubi8/ubi /bin/bash Steps to reproduce as root-less user execute , podman run -it -m 512M registry.redhat.io/ubi8/ubi /bin/bash It results the above error. Expected results expecting to assign the memory limit for a root-less user while running the container. I have also tried to enable cgroup v2 based on the below KB article. https://access.redhat.com/solutions/5502961 but it states " Setting the memory limit for rootless container will not be supported by podman, because for this CGroupv2 needs to be enabled. And if the CGroupv2 will be enabled, podman itself will fail to work. While I enabled cgroup version 2 and executed the command as root-less user [sachisha@rhel8 ~]$ podman run -it -m 512M registry.redhat.io/ubi8/ubi /bin/bash Error: container create failed (no logs from conmon): conmon bytes "": readObjectStart: expect { or n, but found , error found in #0 byte of ...||..., bigger context ...||... It gives error. Regards Sachin
Done
Click on a version to see all relevant bugs
Red Hat Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.