The trick for development is to enable the podman socket (for the user for rootless containers) and then use the standalone version of docker-compose.
I just took a look at the socket activation docs[0]. Is my understanding correct that no `compose.yaml` is required, just running `docker-compose up` with the appropriate env var pointing to the socket is enough to trigger a connection and service activation?
[0] https://github.com/containers/podman/blob/main/docs/tutorial...
As far as I remember my podman installations on both fedora and ubuntu came with a podman.socket service that I could enable as easily as running: `systemctl --user enable --now podman.socket`
Then I installed the standalone version of docker-compose: https://docs.docker.com/compose/install/standalone/
I don't remember having to do more to get a working `docker-compose` command.
Can anyone share their experience with Podman + Docker Compose in recent times? It was a really great workflow for me at the time.
Then you can use docker contexts to make the default context your podman socket. Then you just use `docker compose` as you normally would. I usually use this with rootless podman installs.