3 ms·

The trick for development is to enable the podman socket (for the user for rootless containers) and then use the standalone version of docker-compose.

arcanemachiner 2y ago
I haven't touched this subject for a couple years now, but I remember that this feature was broken for a while after Compose was rewritten (in Go?). Can anyone share their experience with Podman + Docker Compose in recent times? It was a really great workflow for me at the time.
- jeppester 2y ago
  I use it every day, it has been working flawlessly for me for ~2 years.
- robohoe 2y ago
  Just make sure you’re using a relatively new version of Podman, v3 had some issues with sockets on Debian and CentOS
- sureglymop 2y ago
  It works perfectly fine if you install docker but just the CLI (e.g. on debian docker provides a package for that in their deb repository). Then you can use docker contexts to make the default context your podman socket. Then you just use `docker compose` as you normally would. I usually use this with rootless podman installs.
gm678 2y ago
I've been looking for a better solution for local dev on services deployed via quadlet, could you elaborate on this? I just took a look at the socket activation docs[0]. Is my understanding correct that no `compose.yaml` is required, just running `docker-compose up` with the appropriate env var pointing to the socket is enough to trigger a connection and service activation? [0] https://github.com/containers/podman/blob/main/docs/tutorials/socket_activation.md#socket-activation-of-the-api-service https://github.com/containers/podman/blob/main/docs/tutorial...
- jeppester 2y ago
  That is exactly what I do. As far as I remember my podman installations on both fedora and ubuntu came with a podman.socket service that I could enable as easily as running: `systemctl --user enable --now podman.socket` Then I installed the standalone version of docker-compose: https://docs.docker.com/compose/install/standalone/ https://docs.docker.com/compose/install/standalone/ I don't remember having to do more to get a working `docker-compose` command.
- deleted 2y ago
  [deleted]

arcanemachiner 2y ago

I haven't touched this subject for a couple years now, but I remember that this feature was broken for a while after Compose was rewritten (in Go?). Can anyone share their experience with Podman + Docker Compose in recent times? It was a really great workflow for me at the time.

jeppester 2y ago
I use it every day, it has been working flawlessly for me for ~2 years.
robohoe 2y ago
Just make sure you’re using a relatively new version of Podman, v3 had some issues with sockets on Debian and CentOS
sureglymop 2y ago
It works perfectly fine if you install docker but just the CLI (e.g. on debian docker provides a package for that in their deb repository). Then you can use docker contexts to make the default context your podman socket. Then you just use `docker compose` as you normally would. I usually use this with rootless podman installs.

gm678 2y ago

I've been looking for a better solution for local dev on services deployed via quadlet, could you elaborate on this? I just took a look at the socket activation docs[0]. Is my understanding correct that no `compose.yaml` is required, just running `docker-compose up` with the appropriate env var pointing to the socket is enough to trigger a connection and service activation? [0] https://github.com/containers/podman/blob/main/docs/tutorials/socket_activation.md#socket-activation-of-the-api-service https://github.com/containers/podman/blob/main/docs/tutorial...

jeppester 2y ago
That is exactly what I do. As far as I remember my podman installations on both fedora and ubuntu came with a podman.socket service that I could enable as easily as running: `systemctl --user enable --now podman.socket` Then I installed the standalone version of docker-compose: https://docs.docker.com/compose/install/standalone/ https://docs.docker.com/compose/install/standalone/ I don't remember having to do more to get a working `docker-compose` command.
deleted 2y ago
[deleted]