Big thing for me is Podman being daemon-less, making it a lot easier to integrate with existing tools since you don't have to treat it as it's own thing. It's already had easy systemd integration for a while now[0] and with Quadlet[1] I don't even bother writing compose files anymore; I just add a [Container] or [Volume] section to the same unit file templates I use everywhere else and it's all taken care of. Though to be honest, I mostly used bash script over compose files anyway since podman-compose never really worked as well.

Someone else has already mentioned built in pod support, plus you can generate kube files from existing pods for easy deployment.

So you end up with this nice progression of managing:

1. one-off/short term containers with podman run

2. longer running containers with podman generated systemd units

3. generation deployment of above long running containers with Quadlet

4. pods and more complicated setups on one machine with kube files

5. pods and more complicated setups across multiple machines with kubernetes

Which is a really nice stack to work with since they all use the same toolbox.

And that's outside of other small features like not having to worry about the docker package updating restarting the daemon and taking it all down, socket activation (through systemd units), and auto-updates.

[0] https://docs.podman.io/en/latest/markdown/podman-generate-sy... [1] https://docs.podman.io/en/latest/markdown/podman-systemd.uni...