Hi Robert,
I'm not an expert at all. But I had this question a few days ago.
The most common tool seems to be
https://github.com/containers/podman-compose.
Unfortunately, in my case it was not able to replace docker's compose
completely¹.
But podman-compose has a option to trace what it is trying to do. This
helped me, to write a simple script, which is doing the same job as the
initial composer file.
Uwe
¹) Sorry I haven't documented the problem well.
As far as I remember, the problem was that composer creates/runs
standalone containers with different IPs and an implicit DNS service
(container name -> ip). podman-compose creates a pod, which means all
containers in this pod share the IP 'localhost'. Im my case this was a
problem, because the application on one container was looking for
resources on the host 'mysql'.