Podman's systemd-generator doesn't seem to create any service file for backup.pod in /run/user/$(id -u user). I do see a service file for backup.container, backup.service.
Regardless, systemctl start backup.service errors out anyway.
The primary reason why I tried this was because I couldn't figure out how to create a pod using compose.yaml either. If someone has answers to these questions, they would be much appreciated!
Apologies for not answering earlier. I have since switched over to podman generate kube and podman play kube for managing my podman infrastructure. This plays in well with my plans since I can't be dependent on systemd going forward. Thank you for your help.
With that said, I wanted to ask another question: when I try to run a container with podman run debian, it automatically pulls the debian container without a problem, however how is it that when I type podman pull docker.io/debian/debian it requires auth?
Pretty sure that the registry path for official images is "library" (at least it used to be). So it should be "docker.io/library/debian", though I can't double check at the moment.