3 ms·

These days Podman implements the docker API, so it's easier to use docker-compose. I am not sure if there's any compelling reason to use podman-compose any more

• deleted 3y ago
  [deleted]
• pydry 3y ago
  It's kind of a pain to set up a port for docker compose to talk to. podman compose is effectively 90% finished too. It's just annoying seeing some roughness around the edges. I'm not convinced it would be all that hard to make it better than docker compose, either.
  • yrro 3y ago
    I suppose it would be nice if podman.socket was enabled by default. Socket activation means that it wouldn't actaully launch podman-system-service unless something connected to it. For me the problem with podman-compose is that it will be continuously chasing the moving target of what docker-compose is able to do. Hence there will forever be developers trying it out, finding out that "it doesn't work" and, in wanting to just get on with their jobs, going back to docker-compose... and in the process filing "podman" away in that little box in the back of their head of stuff that doesn't work. Implementing the docker API seems to have worked out much better, I suppose it too is a moving target but it seems to move slower; I can at least download some demo docker-compose.yaml files and process them with docker-compose talking to podman and they worked out of the box!