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.

  • anyhow2503@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 day ago

    I would recommend using the docker-compose cli pointed at a podman socket over podman-compose. I don’t think anyone has been recommending podman-compose for quite a while now.

    • EnsignWashout@startrek.website
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 day ago

      Interesting.

      I used to do it the way you’re recommending (before I had podman compose), but I got tired of installing docker compose, and haven’t suffered enough for just using Podman compose, lately.

      I do think more things are more likely to work the way you’re saying. Compose doesn’t seem to be standardized yet? And the original dev was probably using Docker compose - for any randomly selected project.

      But when I can get away with podman compose, I do, as I recall it being much easier to setup.