Issue with conmon 2.1.12 and podman 4.9.4 on Oracle Linux 9.5 in Cron Context

[vixaiganxk]

Description:
I'm encountering an error when executing Podman commands via a cron job on Oracle Linux 9.5. The issue occurs while pulling a container image using podman pull. It works perfectly fine when run manually as the same user (opc), but fails when executed via crontab. The error output is as follows:
Error: container create failed (no logs from conmon): conmon bytes "": readObjectStart: expect { or n, but found , error found in #0 byte of ...||..., bigger context ...||...

Environment:

• OS: Oracle Linux 9.5
• Podman Version: 4.9.4-rhel
• Conmon Version: 2.1.12 (commit: 1239853d34c1fe9a230e88967a9c067e4203b9ea)
• Cron User: opc
• Command Executed via Cron: */2 * * * * podman pull container-registry.oracle.com/os/oraclelinux:8 >> /var/u01/app/tmp/pull_debug.log 2>&1

Command Output When Executed Manually:

• Success (no errors)

Steps to Reproduce:

• Install podman 4.9.4 and conmon 2.1.12 on Oracle Linux 9.5.
• Add the following cron job for the opc user: */2 * * * * podman pull container-registry.oracle.com/os/oraclelinux:8 >> /var/u01/app/tmp/pull_debug.log 2>&1
• Check the cron logs for errors.

Expected Behavior:

• The image should pull successfully when executed via cron, just as it does when run manually.

Observed Behavior:

• The cron job fails with the error: Error: container create failed (no logs from conmon): conmon bytes "": readObjectStart: expect { or n, but found , error found in #0 byte of ...||..., bigger context ...||...