Arch Linux

Description:

After upgrading conmon to 1:2.0.23-1 podman does not work anymore:

DEBU[0021] /usr/bin/conmon messages will be logged to syslog
DEBU[0021] running conmon: /usr/bin/conmon args="[--api-version 1 -c ceb95e35204b52257054493954ec6f5d14caa4b67058dcbf9d49b5ef75b31709 -u ceb95e35204b52257054493954ec6f5d14caa4b67058dcbf9d49b5ef75b31709 -r /usr/bin/runc -b /home/fritz/.local/share/containers/storage/overlay-containers/ceb95e35204b52257054493954ec6f5d14caa4b67058dcbf9d49b5ef75b31709/userdata -p /run/user/1000/containers/overlay-containers/ceb95e35204b52257054493954ec6f5d14caa4b67058dcbf9d49b5ef75b31709/userdata/pidfile -n builder --exit-dir /run/user/1000/libpod/tmp/exits --socket-dir-path /run/user/1000/libpod/tmp/socket -l k8s-file:/home/fritz/.local/share/containers/storage/overlay-containers/ceb95e35204b52257054493954ec6f5d14caa4b67058dcbf9d49b5ef75b31709/userdata/ctr.log --log-level debug --syslog -t --conmon-pidfile /run/user/1000/containers/overlay-containers/ceb95e35204b52257054493954ec6f5d14caa4b67058dcbf9d49b5ef75b31709/userdata/conmon.pid --exit-command /usr/bin/podman --exit-command-arg --root --exit-command-arg /home/fritz/.local/share/containers/storage --exit-command-arg --runroot --exit-command-arg /run/user/1000/containers --exit-command-arg --log-level --exit-command-arg debug --exit-command-arg --cgroup-manager --exit-command-arg cgroupfs --exit-command-arg --tmpdir --exit-command-arg /run/user/1000/libpod/tmp --exit-command-arg --runtime --exit-command-arg runc --exit-command-arg --storage-driver --exit-command-arg overlay --exit-command-arg --storage-opt --exit-command-arg overlay.mount_program=/usr/bin/fuse-overlayfs --exit-command-arg --events-backend --exit-command-arg journald --exit-command-arg --syslog --exit-command-arg container --exit-command-arg cleanup --exit-command-arg --rm --exit-command-arg ceb95e35204b52257054493954ec6f5d14caa4b67058dcbf9d49b5ef75b31709]"
DEBU[0021] Cleaning up container ceb95e35204b52257054493954ec6f5d14caa4b67058dcbf9d49b5ef75b31709
DEBU[0021] Tearing down network namespace at /run/user/1000/netns/cni-d09f5744-bcec-788e-6c12-1e4f879989b1 for container ceb95e35204b52257054493954ec6f5d14caa4b67058dcbf9d49b5ef75b31709
DEBU[0021] unmounted container "ceb95e35204b52257054493954ec6f5d14caa4b67058dcbf9d49b5ef75b31709"
DEBU[0021] Removing container ceb95e35204b52257054493954ec6f5d14caa4b67058dcbf9d49b5ef75b31709
DEBU[0021] Removing all exec sessions for container ceb95e35204b52257054493954ec6f5d14caa4b67058dcbf9d49b5ef75b31709
DEBU[0021] Cleaning up container ceb95e35204b52257054493954ec6f5d14caa4b67058dcbf9d49b5ef75b31709
DEBU[0021] Network is already cleaned up, skipping...
DEBU[0021] Container ceb95e35204b52257054493954ec6f5d14caa4b67058dcbf9d49b5ef75b31709 storage is already unmounted, skipping...
DEBU[0021] Container ceb95e35204b52257054493954ec6f5d14caa4b67058dcbf9d49b5ef75b31709 storage is already unmounted, skipping...
DEBU[0021] ExitCode msg: "container create failed (no logs from conmon): eof"
Error: container create failed (no logs from conmon): EOF

Additional info:
* package version(s): conmon-1:2.0.23-1-x86_64
* config and/or log files etc.: no configuration used, only defaults
* link to upstream bug report, if any: no upstream bug reported

Steps to reproduce:
Upgrade to 1:2.0.23 and try to run any container, i.e. podman run -it docker.io/debian:bullseye bash

Downgrading to 1:2.0.22 solves the problem.