Debian recently packaged 1.0.3 that is also old.
https://wiki.archlinux.org/title/Podman#Docker_Compose
podman-compose is less interesting since.
The podman way is to write a k8s manifest and start it with `podman play kube`. Also handles configMaps and persistentVolumes.
If you really need docker-compose, podman is API-compatible with docker, so you can use the real thing on top of the podman socket.
Just do not use podman-compose.
I used qemu for a while on my old macbook with a linux vm that had ssh installed. You can actually make docker use a remote machine via ssh and with some environment variable magic you can actually make things like docker-compose work that way. A bit tricky with mounting volumes and forwarding ports of course but you can make that work as well. You can use ssh to forward local ports to a remote machine and you can setup qemu to share directories to the vm. It is a bit tedious to manage but I used this for several months with some scripts to set this up. So, having done this manually, that raises the question why Podman can't do this?
I reverted back to using docker desktop when I got my M1 macbook last year. It's just easier. But it would be nice to have some alternative if the need ever arises. If Podman improves their docker-compose support I might give it another try.