211–220 of 269 posts
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.
- What's Docker?
- wow Docker is so convenient
- hmmm all that convenience is creating new problems
- is Docker really open?
- What's Podman?
- Ugh Podman is a great idea but does not work
- Is Podman working better now?
- ... kinda, just for testing on my machine
- wow... Podman works just as well as Docker in 99.99% of my cases
... so yes except for the last .01% (e.g. rather niche https://github.com/containers/podman-compose/issues/792 ) is now my default container engine.
Earlier quoted context omitted.
I switched my home server from k3s to quadlet and saw an 8% drop in power usage.
Well hang on a second I have two nodes running k3s. 8%?? Did you accidentally also swap out the CPU governor?
One thing I don't like about Podman is that it pretends to be docker-compatible while having some minor differences that will come to bite you. And users of your docker-based project who try to run it on Podman will come to you and complain.
I've found most of the differences to come not from the socket API, or the logical behavior, or CLI differences. But instead from assumptions Docker makes, that it's running rootful, when Podman will not (by default). As such, most of the fixes for Podman/Docker incompatibilities is just addressing that assumption with a few extra flags on the Podman commands to change how the user namespace maps between the containe…
Earlier quoted context omitted.
I switched a few years back and use Quadlets instead of compose now. Converting compose files to Quadlets is pretty mechanical once you get the hang of it. Highly recommend Podman overall; there are some quirky edge cases, but for the most part it’s a smooth replacement for Docker. If you don’t want to give up compose entirely, podman-compose exists. I just prefer Quadlets so I haven’t used it much myself.
Do you have a good canonical source on this conversion? I’ve tried the conversion tools that came out around the release of podman v4 and again with v5. But somehow the files being generated contained deprecated features which pointed me to use different commands which led me to yet again different structures which when executed in systemd brought me back to what I originally had. I never got it to work fully.
Earlier quoted context omitted.
I'm sorry this is happening to you. I'm on the team that helped bring podman into the CNCF and I worked on ubuntu for over a decade, this isn't a technical problem this is a business one. Podman is in universe, so Canonical doesn't care unless you pay. Fair enough, good engineers cost money. RH isn't going to pay. Podman engineers would love to be in Ubuntu, the Red Hat engineers would love to directly upload into Un…
I don't claim to understand the business or politics between RedHat and Ubuntu. I do know many projects with way less resources seem to be able to support Ubuntu and other popular distros just fine. Often through PPAs or their own apt repos (like Docker, PostgreSQL, or Incus). If RedHat doesn't choose to, so be it. But IMO, they can't really compete with Docker when getting a recent release on the most popular distro…
It's the distro's job to package and integrate this software with the rest of the system, to make it easier for their users.
I have 1677 packages installed. I absolutely _do not_ want to go to 1677 places to install or look for the latest version.
After Docker Desktop randomly started consuming insane amounts of memory again we switched to Podman and it was literally as easy as installing it and pointing it at our docker-compose.yml. Zero changes needed and now I don’t need to keep a daemon running. Great software.
I liked Orbstack better than colima which was better than Docker Desktop. Then I found https://smolmachines.com's smolvm microvms.
Earlier quoted context omitted.
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.
Podman has supported plugin compose (v2) for years now, and I believe that's the version I used before I switched to Quadlets, but I must have not needed Buildkit features back then because those are apparently still unsupported over v2.
Don't know about that. I did a ddg search "using docker compose (v2) plugin with podman" I do get some tutorials but they all are from 2026. This also aligns with my experience from late 2024 where you where typical advised to use `podman compose` or the compose script.
After Docker Desktop randomly started consuming insane amounts of memory again we switched to Podman and it was literally as easy as installing it and pointing it at our docker-compose.yml. Zero changes needed and now I don’t need to keep a daemon running. Great software.
I liked Orbstack better than colima which was better than Docker Desktop. Then I found https://smolmachines.com's smolvm microvms.
Earlier quoted context omitted.
I went all in on podman compose last year but went all back because off constant permission errors. I thought it was going to be better than docker because I run the containers as a user… but man the amount of time I wasted on files that either I or the container itself or some other container couldn’t read… With docker I felt that stuff just works. And then there are the extra steps: Enable user lingering, make a sy…
what kind of stuff is in your compose?
I wish that "run podman containers as a user, rootless" would just simply mean: All the things are also the property of the user, but you get weird uid/guid combos and stuff on your filesystem as owners you never heard of (like www-data, but not that one in particular) due to the mismatches.
If containers can ever simply be run as user like they are a user process, that would be so nice.