Podman v6.0.0

Post by Zardoz84 » Fri, Jul 03, 2026, 7:05 AM UTC

LinXitoW wrote: post #128

sudonem wrote: post #73

Earlier quoted context omitted.

I’d wager it’s mainly just that deployment is mildly more annoying and requires more disparate steps. Especially if you want to go rootless (and you should). For someone that isn’t “Linux first” (like a baby developer learning to containerize their apps), the idea of dealing with systemd unit files or kublet configs, and having to created dedicated local service accounts (and remembering to enable linger) is somewhat…

It's not just mildly annoying, it completely ruins a great thing. Docker Compose is to stacks what Dockerfiles are to a single application. Podmans solution is to not commit to compose, but instead to create a bespoke mechanism involving a bunch of tiny files, all of which is insanely system (linux) specific, and therefore completely non-portable. I genuinely don't understand how someone can see the value of Docker,…

Post by ShinyLeftPad » Fri, Jul 03, 2026, 7:13 AM UTC

stefr- wrote: post #195

drnick1 wrote: post #173

Earlier quoted context omitted.

> Docker Compose is to stacks what Dockerfiles are to a single application. Podmans solution is to not commit to compose This isn't (completely) true. I found podman-compose to be a more or less drop-in replacement for docker-compose. I know that in the past support was patchy, but things are rather good now.

Pretty sure that's because podman-compose literally calls docker-compose under the hood. e: from the manpage: "podman compose is a thin wrapper around an external compose provider such as docker-compose or podman-compose. This means that podman compose is executing another tool that implements the compose functionality but sets up the environment in a way to let the compose provider communicate transparently with the…

Post by ShinyLeftPad » Fri, Jul 03, 2026, 7:20 AM UTC

raffraffraff wrote: post #79

Chyzwar wrote: post #44

Earlier quoted context omitted.

Last time I evaluated podman, Ubuntu was second class citizen. Rootless was non trivial and required additional setup. Documentation also suck. Docker is something we all already hate, milion edge cases and forever bugs but at least well documented and understood. Podman claim to be drop-in replacement does it mean it carry docker shitness? Examples: ufw punch through, env file handling, volumes, etc

Last time I tried rootless podman was about 6 months ago and it was a total mess. I was trying to use it to run a container as me (user 1000) and mount a directory from my home (owned by user 1000) and it drove me and Claude around the bend. It's not a podman vs docker thing per se, just rootless being a total pain. However I just enabled the docker service, ran the same command on docker and it worked. I think I jus…

Post by znpy » Fri, Jul 03, 2026, 7:40 AM UTC

SwellJoe wrote: post #4

No idea why Docker is still so much more popular than Podman. Podman is obviously the better implementation. The new network stuff is a welcome improvement.

Post by debugnik » Fri, Jul 03, 2026, 7:46 AM UTC

theK wrote: post #184

debugnik wrote: post #70

Earlier quoted context omitted.

You can use actual docker-compose with podman, the -compose projects are separate from podman/docker. podman-compose never worked well for me but docker-compose on podman did.

The CLI plugin or the script? Last time I checked the podman CLI did not support docker CLI plugins and the script is EOL since years.