←back to thread

I ditched Docker for Podman

(codesmash.dev)
1101 points codesmash | 4 comments | 05 Sep 25 11:56 UTC | HN request time: 0.218s | source
Show context
raquuk ◴[05 Sep 25 12:18 UTC] No.45137666[source]▶
The "podman generate systemd" command from the article is deprecated. The alternative are Podman Quadlets, which are similar to (docker-)compose.yaml, but defined in systemd unit files.
replies(2): >>45137744 #>>45137747 #
1. stingraycharles ◴[05 Sep 25 12:29 UTC] No.45137744[source]▶
Which actually makes a lot of sense, to hand over the orchestration / composing to systemd, since it’s not client <> server API calls (like with docker) anymore but actual userland processes.
replies(2): >>45138155 #>>45138441 #
2. solarkraft ◴[05 Sep 25 13:13 UTC] No.45138155[source]▶
It totally does! On the con side, I find systemd unit files a lot less ergonomic to work with than compose files that can easily be git-tracked and colocated.
replies(1): >>45138337 #
3. mariusor ◴[05 Sep 25 13:29 UTC] No.45138337[source]▶
What makes a systemd service less ergonomic? I guess it needs a deployment step to place it into the right places where systemd looks for them, but is there anything else?
4. Cyph0n ◴[05 Sep 25 13:38 UTC] No.45138441[source]▶
Yep. It works even better on a declarative distro like NixOS because you can define and extend your systemd services (including containers) from a single config.

Taking this further (self-plug), you can automatically map your Compose config into a NixOS config that runs your Compose project on systemd!

https://github.com/aksiksi/compose2nix