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.
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 saydockeron 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.
I use the docker compose plugin with podman and it’s the same. My compose stack is massive with tons of services and I migrated it from docker to podman with no issues.
There’s a built in tool to rake docker compose files, and make quqdlets that worked just fine for me?
That’s neat, are you talking about Podlet? Your comment prompted me to search.