I keep reading about podman, yet it doesm’t FEEL as mature to me as docker for a normal user like me. What’s your opinion? Did you already switch or do you keep waiting for … for what? When will you switch?

  • poVoq@slrpnk.net
    link
    fedilink
    English
    arrow-up
    15
    ·
    edit-2
    1 year ago

    Podman is solid, just don’t use podman-compose but rather utilize the Systemd integration for container management.

    With very few exceptions, it works just as well as Docker these days.

    • lemmyvore@feddit.nl
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      3
      ·
      1 year ago

      utilize the Systemd integration for container management.

      The systemd integration is probably the thing I dislike most about it. 😆 Systemd has no business managing containers IMO, it should manage podman and podman should manage the containers. It’s a completely gratuitous mix of concerns but it seems that podman is set on becoming a systemd subsystem… so I’ll probably never use it.

      On a related note, the systemd expansion is getting ridiculous. It’s gotten to the point if you read one day that wayland is being merged into systemd you wouldn’t even know if it’s a joke.

      • kopper [they/them]@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        1 year ago

        One of the reasons I use containers instead of installing things directly is that i can completely uninstall a service by deleting a single directory (that contains a compose.yml and any necessary volumes) and running a docker/podman system prune -a

        or that i can back up everything by backing up a single “containers” dir, which i could have on a subvolume and snapshot if i wanted to

        systemd/quadlet on the other hand makes me throw files in /etc (which is where you’re supposed to put them, but ends up resulting in them being tangled together with base system configuration often partially managed by the package manager)

        The Solution™ to this is configuration management like ansible or whatnot, which needlessly overcomplicates things for the use cases i need (though they’re still useful for getting a base system “container ready” wrt ssh hardening and such)

        tldr: i want my base system to be separated from my services, and systemd integration is the exact wrong tool for this job

      • poVoq@slrpnk.net
        link
        fedilink
        English
        arrow-up
        11
        ·
        1 year ago

        A container is a service, makes perfect sense for me to manage that via Systemd like all other services.

        • lemmyvore@feddit.nl
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          2
          ·
          1 year ago

          Sure, anything can be a service if you want it to be hard enough. Like the bootloader.