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.

  • Voytrekk@sopuli.xyz
    1·
    2 days 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·
      2 days 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·
        2 days 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.