2 ms·
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 activatio
by 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 agoThat 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]