submitted 3 weeks ago* (last edited 3 weeks ago) by to c/linuxmemes@lemmy.world
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] 31 points 3 weeks ago (6 children)

I'm curious why you feel this way? I'm kinda the opposite — podman has features I use that Docker doesn't.

  • source
  • hideshow 6 child comments
  • [–] 9 points 3 weeks ago (3 children)

    Not the poster, but I kinda get this sentiment. For my laptop and things that I do for work, I prefer Podman. Better security posture out of the box, and I'm typically crafting my own pods to work a specific way.

    But, if I am just trying to start up some app/service and I'm following the GitHub documentation with the project...I want to just copy and paste and there isn't a 1-for-1 for docker compose. Podman does have an alias package so you can say docker on the cli, but the "compose" part of it is not as good if I just want something to run without dicking with it.

    So in short, if I'm making something with a container or want to have hands on control, I prefer Podman. If I'm running something "off the shelf", like just running someone's docker compose files files from their Github, I'm just running Docker man.

  • source
  • parent
  • hideshow 3 child comments
  • [–] [S] 1 point 3 weeks ago (1 child)

    This meme was inspired by my frustration from trying to switch. I like the idea of podman, but it just doesn’t work. Tbf the bugs I encountered this time were with podman compose rather than podman itself, but still, I’d rather use the tools that work. I’ve had similar experiences when I’ve tried to switch to podman in the past.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 3 weeks ago

    Interesting. I don't use any of the compose tools, so I've not faced that. I find Podman works reliably in places where I can't even get Docker to start working (such as RISC-V machines), but I also typically use podman for testing before deploying to k8s

  • source
  • parent