Live data from Hacker News

Podman v6.0.0

blog.podman.io

31–40 of 269 posts

Re: Podman v6.0.0

#31
post #6

Anyone have experience switching from Docker to Podman? I have a lot of compose files in my homelab/automation setup and those are what I’m most concerned about.

Good for the most part, I appreciate them being pretty much a drop in replacement (mostly so tools that reference docker can just work usually ). Regardless it works enough for me to run local Kubernetes and Tilt

I have a few containers at home and switched to podman, it was a pleasant surprise to see how how easy it was to drop it in as a replacement.

Re: Podman v6.0.0

#32
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.

Most people simply do not care. They just want a Dockerfile to become an image, and they want to run that image. I use both... rootless podman is nice. Although the promise of ez systemd integration is a bit... oversold. I use it with systemd however with my own hand-crafted unit files. Pretty good combo.

Re: Podman v6.0.0

#33
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.

I think a stronger brand name. Also on macOS I found Docker Desktop to be more straightforward. Also lately it has been very error prone. Randomly failing at mounting files, or cleaning up networking rules, or suddenly becoming bog slow so I have to restart the VM.

Podman on macOS feels miles less refined. Orbstack is a way better choice.

I only use podman on Linux and there it is blazing fast. Even so, most features seem to be geared to be able to replace kubernetes in combination with systemd. And then something simple as docker compose support is flaky and it’s TUI/ux lags behind the original.

Re: Podman v6.0.0

#34
post #6

Anyone have experience switching from Docker to Podman? I have a lot of compose files in my homelab/automation setup and those are what I’m most concerned about.

You don't have to fully switch. I use podman in socket mode with the docker cli as a frontend.

> You don't have to fully switch

Having a heterogenous fleet can be annoying though, some Podman-only config values[1] stop Docker dead in its tracks because it hates unknown fields.

1. It was a while back, and I can't remember what specific field it was, but it had to do with namespacing and/or (sub)UID mapping.

Re: Podman v6.0.0

#35
post #6

Anyone have experience switching from Docker to Podman? I have a lot of compose files in my homelab/automation setup and those are what I’m most concerned about.

Swapped a few years back (pre 5.0), haven't looked back. For compose files I'd look into using quadlets.

For quick conversions you can use compose files directly with podman-compose or docker compose pointed at the podman socket[0].

There's also podlet[1] which converts compose files into native quadlets. It does a pretty good job of taking care of everything for you and for a lot of simple to medium complexity compose files it will Just Work. There's talk of making it into a library of some kind so other tools can transparently convert compose files to quadlets so hopefully we'll see more stuff like it.

Otherwise, writing your own Quadlet files isn't too hard if you're at all familiar with systemd unit files. Most `docker run` or `podman run` arguments have direct quadlet conversions so once you get used to the INI format versus yaml it's pretty easy to see a compose file and churn out the equivalent quadlet(s).

[0] https://www.redhat.com/en/blog/podman-docker-compose

[1] https://github.com/containers/podlet

Re: Podman v6.0.0

#36
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.

For the company I work at, it’s primarily inertia. We started using containers with Docker. And then it just continued. We are two out of 20+ developers who would like to use Podman, but the rest is just ”eh, why bother?”. And I don’t fully fault them for holding that position, Docker generally works. Why switch to something which may or may not provide some benefit (most which will be indirect such as better security and setup)? I still continue to mention Podman regularly though …

Re: Podman v6.0.0

#37
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.

In many places it doesn't matter, because cheap companies don't want to even hear about Docker, so one gets to choose between podman, rancher, and if on Windows wslc is going to be a thing.

Docker (the company) lost the plot in Linux containers, OCI got standardized, alternative runtimes came to be, and very few companies actually care to pay for Docker Desktop or the other services they sell.

Re: Podman v6.0.0

#38
post #6

Anyone have experience switching from Docker to Podman? I have a lot of compose files in my homelab/automation setup and those are what I’m most concerned about.

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.

Re: Podman v6.0.0

#39
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.

I gave up on Podman for some minor reasons: one was that they decided to deviate from Docker and handle SELinux differently, which required effort to change the SELinux security labels on a stock Centos system. That made it a no go.

The other issue is minor differences from Docker, but small enough that a packaged up Docker compose doesn’t work out of the box. It’s not a good use of my time to debug that when I could just switch to Docker, have it work, and get on with my day.

Post reply on HN