containers/podman-compose

podman-compose [0] is a mostly drop-in replacement for local usage, but I have no idea if it works remotely. "podman image scp" [1] looks like it could be helpful though. [0]: https://github.com/containers/podman-compose [1]: https://docs.podman.io/en/latest/markdown/podman-image-scp.1.html

It works but it's not a real drop-in replacement in my experience. I have issues such as [1] where Podman compose seems to leave containers in a dirty state and subsequent `podman compose up` generate odd errors like: > Error: creating container storage: the container name "..." is already in use by [hash]. You have to remove that container to be able to reuse that name: that name is already in use, or use --replace to instruct Podman to do so. And then you try to run `podman compose up --replace` except that's not a recognized argument, so eventually you figure out that you have to run `podman compose down` to clean whatever state is causing issues. I find that I have to do that every tim…

Looks like the compose `watch` option is not yet supported[1]. Huge blocker for adoption in local development. [1]: https://github.com/containers/podman-compose/issues/792

Which compose? Podman-compose [1] wasn't fully up to date with the latest compose-spec [2] the last time I checked it. However, the docker-compose v2 [3] (the one in Go, not Python [4]) is compatible with the Podman engine [5] and works like a charm for me. I have also had no issues with networking, permissions or volumes while running as non-root user. Are you simply facing issues setting it up, or are you hitting some bugs or missing features? [1] https://github.com/containers/podman-compose [2] https://compose-spec.io/ [3] https://github.com/docker/compose [4] https://github.com/docker/compose/tree/v1 [5] https://www.devopsroles.com/how-to-use-docker-compose-with-podman-on-linux/