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.

  • cunnililgus@sopuli.xyz
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    2 days ago

    Definitely, but then it feels like it comes with a cost rather than benefit of not having a daemon. You gain more control at the cost of convenience.

    • pjusk@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 days ago

      Keyword there being “feel”. Cos it certainly does add security. Imo quadlets are easier to understand and write than compose files too, but to each thwir own ofc. Most important thing here is to work with what feels the most natural and making the best out of it 👍

      • cunnililgus@sopuli.xyz
        link
        fedilink
        arrow-up
        1
        ·
        1 day ago

        I understand that to admins or experienced users service files probably feel like home. To an inexperienced user like me it added quite a lot of friction, especially compared to docker where I pretty much copy the compose file and run it.

        I tried to use podman instead of docker, but decided that for my home use it might not be worth the headache, but I might reconsider now that I could use LLM to set those up for me.