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.

  • hirihit640@sh.itjust.worksEnglish
    2·
    2 days ago

    I remember trying it and my compose files blew up to multiple Quadlet files with a much larger total size (lines of code). I find that compose is just more concise and structured compared to Quadlets.

    • Voytrekk@sopuli.xyz
      5·
      2 days ago

      It does have a larger file size compared to compose, sure. The big advantage of quadlets is that systemd will handle things in the event of a failure. It makes it a great option for production environments where you will not need to update your config files as much. It also allows you to have more control over when each application starts, if they rely on a specific disk mount or service running on the system. I’m sure someone else can provide more benefits who use them in a production environment.

      • hirihit640@sh.itjust.worksEnglish
        1·
        1 day ago

        Fair enough. My requirements are simply: start all services when the machine has finished booting. And I can’t remember the last time my system failed. Most that happened was a power outage, and Quadlets wouldn’t have helped there either.

        So in my case I much prefer simple and easy-to-read configs, over the complexity of integrating with systemd.

        • Voytrekk@sopuli.xyz
          1·
          12 hours ago

          Docker compose definitely works for most people, so I would feel pressured to swap.

          There is one instance where Quadlets would have fixed an issue we ran into at work. We had a Kafka instance whose container died and went away because we ran out of space on the server. Compose doesn’t recreate containers on failure, so I was called in to fix the issue. Quadlets treats containers as disposable, so it would have recreated it as soon as it went away. The root of the issue was a bad logging config that we fixed on the next business day.

          • hirihit640@sh.itjust.worksEnglish
            1·
            12 hours ago

            Compose doesn’t recreate containers on failure

            Isn’t it just restart: always in the config? Unless you’re talking about podman, where you also need the podman-restart systemd service.

            • Voytrekk@sopuli.xyz
              1·
              1 hour ago

              You are correct that they restart a container that has stopped because of a bad exit. I meant a container that has completely disappeared due to running out of storage on the system. Given, that is a failure of configuration to begin with.