Some years ago, I started using #Docker #rootless for my #selfhosting needs. I was quite happy with it, even if finding information about rootless mode has been quite difficult.
I mostly used #compose setups.
Some days ago, I looked at #podman to replace those setups with a more modern stack. Podman works well for single containers but not that much podman-compose: don't believe the articles telling you that it's automatic, it's not!
Containers could not communicate together and the solution is to get rid of the compose file, create a pod (exposing network ports) and run the containers inside it.
This is working well but the setup needs to be documented elsewhere (the compose.yaml was sufficient before).
With systemd per-user (lingering), podman pods/containers continue to run after logout.
But what happens after a reboot? You need to either
1. `podman generate systemd` which output long and awful systemd units
2. look at quadlets, which I was going to do before I found
3. read https://www.reddit.com/r/podman/comments/1hau1qt/podman_automatically_start_containers_on_boot/ and copy the `podman-restart.service` in your systemd user setup: simple, easy, I like that!
I think I will migrate my other services one by one if no other problem appears.
One caveat: the podman documentation is really bad and you need to search everywhere to find what I think is basic information (like what to migrate compose to, or how to create quadlets...).
@daks
This is my go to page: https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html
Make sure you set the right version on the bottom right.
Examples are on the end of the page
Éric
Christian