EDIT: For some context, I recently gave podman another go. I have a few services on my homelab server set up in docker containers, so I tried migrating to podman.

After the second major bug (open issue on github) I encountered looked like it would require completely dropping using compose files to work around, I gave up and went back to docker.

I like the idea of podman, but it’s just not stable. I’ll try again in a year or so.

As a bonus, docker’s CLI is significantly nicer.

      • esc@piefed.social
        link
        fedilink
        English
        arrow-up
        55
        arrow-down
        1
        ·
        18 days ago

        Rootless, better integrated with system, a bit faster and lighter on resources. Also it supports k8s style yaml configuration both ways and a lot of people are more familiar with them and they also provide some (minimal) interoperability.

        • lemmyvore@feddit.nl
          link
          fedilink
          English
          arrow-up
          2
          ·
          16 days ago

          Not requiring a service running in root context.

          I don’t think I’ve ever understood the distinction in this argument.

          Isn’t systemd exactly that, a service running in root context?

          I mean yeah you can technically run podman containers by hand as a non-privileged user but nobody does that, let’s be serious. Everybody uses systemd for management and autostart.

          I really don’t understand how running a container through docker as a non-privileged user and dropping all caps is any different from doing the same through systemd + podman.

          Tons of other services do that, ssh, CUPS etc.

          If anybody can explain the difference I’d appreciate it.

      • terminatortwo@piefed.social
        link
        fedilink
        English
        arrow-up
        39
        arrow-down
        1
        ·
        18 days ago

        At work, avoiding surprise licensing fees. If you ever have over 250 employees or over 10 million revenue, you owe a subscription.

        At the home, easy orchestration with systemd

          • JackbyDev@programming.dev
            link
            fedilink
            English
            arrow-up
            5
            ·
            edit-2
            17 days ago

            Yes. Rancher desktop exists, btw. Just an fyi.

            Edit: An open source alternative to Docker Desktop. It has most of the same features. Occasionally I’ve run into something that doesn’t work, but for the most part it’s just peachy.

          • terminatortwo@piefed.social
            link
            fedilink
            English
            arrow-up
            4
            ·
            18 days ago

            It is! If you want to reduce exposure to this you really have to make sure mdm disallows installing it. The numbers trigger regardless of seats, and then you’re on the hook for the licenses for every employee using it.

            So even if as a matter of policy you don’t use docker desktop, it’s possible engineers still do.

          • TerHu@lemmy.dbzer0.com
            link
            fedilink
            arrow-up
            1
            ·
            18 days ago

            if you’re asking with regards to systemd orchestration, no. i love deploying containers as Ansible -> systemd -> podman.