u/Due-Author631

I know it's deprecated, but I'm trying to figure out why this isn't working for me. I'm studying for the ex188 and when I use the --new flag generating off a created pod with containers, the pod and containers doesn't start after reboot, journalctl -xeu is blank.

# pod-webapp.service
# autogenerated by Podman 5.6.0
# Sun May  3 09:16:32 EDT 2026

[Unit]
Description=Podman pod-webapp.service
Documentation=man:podman-generate-systemd(1)
Wants=network-online.target
After=network-online.target
RequiresMountsFor=/run/user/1000/containers
Wants=container-app-mariadb.service container-app-nginx.service
Before=container-app-mariadb.service container-app-nginx.service

[Service]
Environment=PODMAN_SYSTEMD_UNIT=%n
Restart=on-failure
TimeoutStopSec=70
ExecStartPre=/usr/bin/podman pod create \
--infra-conmon-pidfile %t/pod-webapp.pid \
--pod-id-file %t/pod-webapp.pod-id \
--exit-policy=stop \
-p 8080:80 webapp
ExecStart=/usr/bin/podman pod start \
--pod-id-file %t/pod-webapp.pod-id
ExecStop=/usr/bin/podman pod stop \
--ignore \
--pod-id-file %t/pod-webapp.pod-id  \
-t 10
ExecStopPost=/usr/bin/podman pod rm \
--ignore \
-f \
--pod-id-file %t/pod-webapp.pod-id
PIDFile=%t/pod-webapp.pid
Type=forking

[Install]
WantedBy=default.target

When I create the service files without the --new flag everything starts correctly, but this is not the answer given in the materials since it is reusing the pod.

It seems like ExecStopPost isnt actually removing the pod and when it goes to build the new one on restart/reboot it conflicts and fails. If I stop the service, remove the pod, and then restart the service, then it seems to work.

I know I could use a .kube and quadlets, but I'm mostly concerned with getting this to work in the expected way for the exam, which does not mention quadlets.

Thanks in advance for any insight.

I know it's deprecated, but I'm trying to figure out the flaw in my logic. I'm studying for the ex188 and when I use the --new flag generating off a created pod with containers, the pod and containers don't start after reboot, journalctl -xeu is blank.

When I create the service files without the --new flag everything starts correctly, but this is not the answer given in the materials.

Is this because it's creating the pod new but the containers aren't being created or in conflict?

Sorry I'm not at my lab to give my specific files.

I know I could use a .kube and quadlets, but I'm also having issues getting the service files to generate. But I'm mostly concerned with getting this to work in the expected way for the exam, which does not mention quadlets.

Thanks in advance for any insight.