12 ms·

The "podman generate systemd" command from the article is deprecated. The alternative are Podman Quadlets, which are similar to (docker-)compose.yaml, but defin

by raquuk 1y ago

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.

stingraycharles 1y ago
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.
- solarkraft 1y ago
  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.
  - mariusor 1y ago
    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?
- Cyph0n 1y ago
  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 https://github.com/aksiksi/compose2nix
broodbucket 1y ago
With almost no documentation, mind
- raquuk 1y ago
  I find the man page fairly comprehensive: https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html https://docs.podman.io/en/latest/markdown/podman-systemd.uni...
  - tux1968 1y ago
    Is linking to a 404 page meant to highlight the lack of docs, or is there some mistake?
    - raquuk 1y ago
      Apparently the documentation was just updated. The new location is https://docs.podman.io/en/latest/markdown/podman-quadlet.7.html https://docs.podman.io/en/latest/markdown/podman-quadlet.7.h...
      - mdaniel 1y ago
        I do believe you about the "updated" part, and that's a constant hazard with linking to "latest" or "main" of anything. But I don't know why you'd then change the actual file in the URL, since the original comment was citing "podman-systemd.unit.5.html" <https://docs.podman.io/en/v5.6.1/markdown/podman-systemd.unit.5.html https://docs.podman.io/en/v5.6.1/markdown/podman-systemd.uni...> and you've chosen to cite quadlet.7
        stryan 1y ago
        Not OP but "podman-systemd.unit.5" used to be the primary Quadlet documentation (a remnant of when it was podman-generate-systemd perhaps?) with every Quadlet file type (.container, .volume, .network, etwc) documented on one page. The new docs split that out into separate podman-container/volume/etc.unit(5) pages, with quadlet.7 being the index page. So they're still linking to the same documentation, just the organization happened to change underneath them. If you must see what they linked to originally, the versions docs are still the original organization (i.e. all on one page): https://docs.podman.io/en/v5.6.0/markdown/podman-systemd.unit.5.html https://docs.podman.io/en/v5.6.0/markdown/podman-systemd.uni...

by raquuk 1y ago

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.

stingraycharles 1y ago

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.

solarkraft 1y ago
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.
- mariusor 1y ago
  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?
Cyph0n 1y ago
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 https://github.com/aksiksi/compose2nix

broodbucket 1y ago

With almost no documentation, mind

raquuk 1y ago
I find the man page fairly comprehensive: https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html https://docs.podman.io/en/latest/markdown/podman-systemd.uni...
- tux1968 1y ago
  Is linking to a 404 page meant to highlight the lack of docs, or is there some mistake?
  - raquuk 1y ago
    Apparently the documentation was just updated. The new location is https://docs.podman.io/en/latest/markdown/podman-quadlet.7.html https://docs.podman.io/en/latest/markdown/podman-quadlet.7.h...
    - mdaniel 1y ago
      I do believe you about the "updated" part, and that's a constant hazard with linking to "latest" or "main" of anything. But I don't know why you'd then change the actual file in the URL, since the original comment was citing "podman-systemd.unit.5.html" <https://docs.podman.io/en/v5.6.1/markdown/podman-systemd.unit.5.html https://docs.podman.io/en/v5.6.1/markdown/podman-systemd.uni...> and you've chosen to cite quadlet.7
      - stryan 1y ago
        Not OP but "podman-systemd.unit.5" used to be the primary Quadlet documentation (a remnant of when it was podman-generate-systemd perhaps?) with every Quadlet file type (.container, .volume, .network, etwc) documented on one page. The new docs split that out into separate podman-container/volume/etc.unit(5) pages, with quadlet.7 being the index page. So they're still linking to the same documentation, just the organization happened to change underneath them. If you must see what they linked to originally, the versions docs are still the original organization (i.e. all on one page): https://docs.podman.io/en/v5.6.0/markdown/podman-systemd.unit.5.html https://docs.podman.io/en/v5.6.0/markdown/podman-systemd.uni...