> - Does this mean we don't have to install docker-compose to run compose.yml files?
yes, you don't have to
there are key differences and advantages for each
the key differences originate from that
* docker and docker-compose are based on fat daemon model
* podman and podman-compose are based on process model
you can run podman as a daemon and use docker-compose by pointing to the daemon
but you lose all the advantages of the process model.
here are some information
basically, podman-compose just run podman which runs the container or build as the current user
in podman there is no overhead of communication (ex. if you want to build a container in a 1GB project, docker will creates 1 GB tarball and send it to the remote daemon and the daemon will extract that archive)
in podman there is no security implications, while in docker things are executed by the remote daemon (which is most likely root)
> - docker-compose works decently in production environment. What is the roadmap for making podman-compose usable in production?
podman-compose just calls podman
there is no heavy lifting done by podman-compose
my plan to podman-compose is to make it support "podman network create" instead of the current old workaround of single pod network.