Test with podman-4.4.0-1.el9.x86_64. Use https://github.com/containers/podman-compose/tree/devel/examples/azure-vote to start the podman-compose.
Run podman-compose up under the azure-vote and wait it fully start
# podman-compose up
In another console run podman ps -a for several times as it is mentioned in the issue and check the dbus-daemon numbers with ps:
[root@dell-per430-09 ~]# ps -ef | grep dbus-daemon | wc -l
1
[root@dell-per430-09 ~]# podman ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a3c4a08d20eb mcr.microsoft.com/oss/bitnami/redis:6.0.8 /opt/bitnami/scri... 21 minutes ago Up 12 minutes azure-vote-back
659a474532b4 mcr.microsoft.com/azuredocs/azure-vote-front:v1 /start.sh 12 minutes ago Up 12 minutes 0.0.0.0:8080->80/tcp azure-vote_azure-vote-front_1
[root@dell-per430-09 ~]# podman ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a3c4a08d20eb mcr.microsoft.com/oss/bitnami/redis:6.0.8 /opt/bitnami/scri... 21 minutes ago Up 12 minutes azure-vote-back
659a474532b4 mcr.microsoft.com/azuredocs/azure-vote-front:v1 /start.sh 12 minutes ago Up 12 minutes 0.0.0.0:8080->80/tcp azure-vote_azure-vote-front_1
[root@dell-per430-09 ~]# ps -ef | grep dbus-daemon | wc -l
1
The number of dbus-daemon is not changed. So move it to verified.
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 (Moderate: podman security and bug fix 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-2023:2282