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
      5
      ·
      edit-2
      15 days ago

      Probably as good as it can, you shouldn’t use docker compose with podman anyway, there are two alternatives (quadlets - they describe everything as a systemd units and kube yaml - they use standard k8s yaml files including pods, deployments, secrets, etc.), both arguably better than compose.

    • andho@lemmy.zip
      link
      fedilink
      arrow-up
      4
      ·
      15 days ago

      I’ve always had issue with podman-compose. So I setup a podman socket and use it with docker compose.

      • EnsignWashout@startrek.website
        link
        fedilink
        arrow-up
        1
        ·
        15 days ago

        Haha. Yes. This meme would be more fair to call “podman compose” out as “we have Docker compose at home”.

        I’m not a fan of the compose pattern anyway. So it doesn’t usually bother me.

      • EnsignWashout@startrek.website
        link
        fedilink
        arrow-up
        1
        ·
        15 days ago

        That’s one thing - installing and trying out Podman compose takes less time than remembering where to get Docker compose from.

        I always at least try it first, because it’s not expensive to try.