3 ms·
Half of the point of podman was to avoid the need to run things with root. Docker compose expects me to have a server running. While I technically could run "p
by pydry 3y ago
Half of the point of podman was to avoid the need to run things with root.
Docker compose expects me to have a server running. While I technically could run "podman system service" and configure docker compose to point at a non-standard socket or port in order to run it I would really prefer not to have that kind of headache just to run a script.
Docker compose was also written by docker and exhibits similar levels of shoddiness to docker. The accumulation of bad design decisions by docker is, indeed, why podman exists in the first place. With a little bit of love podman compose could easily surpass docker compose.
- timost 3y agoI agree with you on the state of podman compose. I just wanted to clarify that you can run docker-compose with podman in _rootless_ mode. This can be done by running podman's systemd user service.
- pydry 3y agoFWIW I actually tend to run podman compose inside a podman container. This is so I can containerize the integration tests which orchestrate the app. It's a useful pattern - one I think should be a lot more widely used for several reasons. The systemd service wouldn't work in this context. I could maybe use some entrypoint magic to run a server when the container starts just so I can use docker compose but still...eww. Running a podman systemd service might suffice if it was something that could be installed with a snap of two fingers on every environment but if it means fscking around with service files it's definitely not something I'd want to add to a "set up a development environment" README.
- timost 3y agoI see, interesting. I guess you are saying that systemd service wouldn't work because it's not available inside the container. FWIW it's possible to run a rootless podman container with a working systemd inside the container. I've near tried running podman in podman using systemd though.