Hacker News Reader

Comment by pydry | Hacker News Reader

podman compose is really bad

Indeed, it has a lot of limitations. It's better to use docker compose with a podman socket.

Interesting; I have yet to run into any issues with it. Teams I work with mostly use it for local development/testing and do actual deploys using Kubernetes, so we don't use Docker Compose for deployments that utilize features unavailable in Podman Compose.

I'll try to do some more testing between the two and edit my original comment with my findings!

Or just use docker until podman compose gets fixed.

After all the whole point was supposed to be that it didnt need a daemon.

How so? What problems do you have with it?

Missing features, lots of debugging spam which cant be turned off, doesnt properly adhere to the compose spec...

Which features specifically? I can't find a conclusive list anywhere. Other than searching GH issues for bugs like: https://github.com/containers/podman-compose/issues/655#issu...

RE debugging spam, the only thing I can think you're referring to can be turned off by setting `export PODMAN_COMPOSE_WARNING_LOGS=false`.

I'm also curious how it doesn't adhere to the spec. I don't doubt you, but it'd be cool if there was a test suite or audit tool that could document that.

I havent tried in a while so I just tried my project again and ran into one missing feature straight away: podman-compose cp

It's basic shit like this which they could fix very easily but I think they just want to push you to use quadlets (systemd).

It never works on first go, constantly debugging and breaking

Reply on news.ycombinator.com