podman-compose down prevents systemd service from starting due to missing CIDFile

[runbmp]

Describe the bug Generating systemd units from a podman-compose container does not work after taking down the container. See the sequence of trouble commands:

podman-compose up -d
podman generate systemd --new --name --files photoprism
mv container-photoprism.service ~/.config/systemd/user
systemctl --user enable --now container-photoprism.service

then you end up with

May 06 10:28:39 600sff podman[3378509]: Error: error reading CIDFile: open /run/user/1000/container-photoprism.service.ctr-id: no such file >
May 06 10:28:39 600sff systemd[1046]: container-photoprism.service: Control process exited, code=exited, status=125/n/a
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStopPost= process belonging to unit UNIT has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 125.

This could very well be user error, but why does the systemd unit require some remnant from podman-compose to work. If I use podman-compose stop instead of podman-compose down I do not have this issue.