as I said, creating an infra with "--share=" (to be able to set different hostnames) will cause podman pod ps to show status degraded

> We need one top-level service to manage the pod. 

if the above is solved, I might go with this

this is the part you are talking about

Description=Podman pod-pod_test.service
Requires=container-test_web80.service container-test_web90.service
Before=container-test_web80.service container-test_web90.service

ExecStart=/usr/bin/podman start 5f2458ba5eac-infra
ExecStop=/usr/bin/podman stop -t 10 5f2458ba5eac-infra
ExecStopPost=/usr/bin/podman stop -t 10 5f2458ba5eac-infra

in case of no infra we can make this part Type=oneshot
or make it the pid of "podman wait" as below

> We could tie it to the first container in the pod but that may not be a generic solution

I would like to be able to make it the pid of  "podman wait test_web80 test_web90"

in my use case, it's a development stack of multiple containers (eg. wordpress, mysql, memcache)
some users want the exit condition to be

1. any container stopped
2. all containers stopped
3. specific container stopped

On Thu, Feb 24, 2022 at 11:44 AM Valentin Rothberg <> wrote:
Hi Muayyad,

Thanks for reaching out.

On Wed, Feb 23, 2022 at 8:26 PM Muayyad AlSadi <> wrote:

when creating a pod with nothing shared and without infra

podman generate systemd -n pod_test
Error: error generating systemd unit files: Pod "pod_test" has no infra container

here is the full commands

podman pod create --name=pod_test --infra=false --share=
podman network create pod_net
podman run --name=test_web80 -d --net pod_net --hostname web80 --pod=pod_test busybox httpd -f -p 8080 -h /etc
podman run --name=test_web90 --requires=test_web80 -d --net pod_net --hostname web90 --pod=pod_test busybox httpd -f -p 9090 -h /etc
podman pod ps

9a894043a1e1  pod_test        Running     18 seconds ago              2

if we replace 

podman pod create --name=pod_test --infra=false --share=


podman pod create --name=pod_test  --share=

podman pod ps

would display Degraded

5f2458ba5eac  pod_test        Degraded    18 seconds ago  a3a4ca1b8e4d  3

if we remove --share=
it would complain about multiple hostnames

what do you suggest?

Using a pod with an infra container will resolve the issue.
and why systemd care about infra?

We need one top-level service to manage the pod. The infra container is the main PID of the `pod.service`. As long as the pod is running, the infra is running. Without that, there is no generic way of tracking and managing the life cycle of the pod.

We could tie it to the first container in the pod but that may not be a generic solution: if this container exists, the entire pod would falsely be marked as exited regardless of other containers in the pod which might still be running.

Kind regards,
Podman mailing list --
To unsubscribe send an email to