Live data from Hacker News

Podman v6.0.0

blog.podman.io

221–230 of 269 posts

Re: Podman v6.0.0

#221

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.

My #1 complaint by far is that it --- pretty much silently --- depends on systemd to work correctly.

Try having a docker-compose with a service that waits until a dependency is healthy --- in a host that has no systemd (such as Alpine Linux).

The service will never start because Podman relies on systemd (and only systemd) to do the periodic healthchecks which it needs to do in order to handle such dependencies.

And of course, this fact isn't adequately documented anywhere. And Red Hat says they'll never, ever drop this dependency.

---

But I don't know if there are any tools compatible with the Docker ecosystem other than Podman. I'd love to find one.

Re: Podman v6.0.0

#222
post #21
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 from Docker to rootless Podman for our build server. Completely positive experience so far. Our builds went _down_ from 1 minute to 2 seconds. I'm also using podman-compose that is small and delightful (I had to fix a few bugs there). It's just one Python file that you can copy.

> Our builds went _down_ from 1 minute to 2 seconds.

Just curious, what might be the cause of such speedup?

Re: Podman v6.0.0

#223
post #38

Earlier quoted context omitted.

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.

Have you tried podlet[0]? Not entirely sure if it's compatible with podman v6 [0] https://github.com/containers/podlet

Yes. I think podlet was one of the tools that the output of podman, or the quadlet tool, suggested I use.

I will try again. Currently I have a systemd service that tries to start my services with `podman compose `. Sometimes this fails, when I start the service interactively it just works. Unknown what exactly is the issue.

Re: Podman v6.0.0

#224

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…

> I went all in on podman compose last year but went all back because off constant permission errors. The issue is that "ease of use" and "it just works" come at the expensive of security and the principle of least privilege. Docker makes things easy by running a daemon as root. Rootless Podman forces you to think about permissions and does not stab you in the back by overwriting your firewall rules.

Yes, the firewall rule altering was what drove us to podman! Was kind of weird to find a container's Postgres wide open on 5432 after a `sudo ufw default deny`. Madness really.

But as said below, the permissions issues got to us.

Re: Podman v6.0.0

#225

Earlier quoted context omitted.

And that issue shows the problem with OSS. Nothing is ever good enough. > Please report this to your distribution And the reply: > but you could create your own .deb packages for each github release, which can be installed much quicker than downloading and compiling source code and all its dependencies. This is why OSS maintainers have burn out. Always wanting more and more. Not even the source code is good enough.

My point is that it's not good enough to compete in this space. Look at the distros that Docker supports. That kind of support is what users expect. When Podman just leaves it up to the distros to support, it's understandable. But, yes, it's not enough.

> That kind of support is what users expect.

Then they should also expect enshittification and rug-pulls when it's realised where motivation for that support comes from.

Re: Podman v6.0.0

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

podman-compose has gotten much better. I used it for a work project a few months ago, and it ran fine. That said, I know there are some random little things podman-compose doesn't support, so be careful.

What I'm experimenting with right now is defining stuff with a Kubernetes yaml, which podman also supports: https://docs.podman.io/en/latest/markdown/podman-kube.1.html.

It's slightly more verbose than docker-compose, but podman supports it natively and you can actually wrap your app containers into a single "pod" for easier management.

Re: Podman v6.0.0

#227
It is a bit buried, but Podman now follows the UAPI Configuration Files Specification as well as the Base Directory Specification. This is great!

Re: Podman v6.0.0

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

Switching quickly turns into "Here is a list of 10 easy steps..."

For anyone with a working homelab there is no reason to switch

If you're worried about security, both need extra work

Re: Podman v6.0.0

#229

I don't understand how podman can be used for serious development work. Sure, if you want to be bound to one single platform (linux), and create a bunch of individual files, you can sort of get something a little bit like compose. But the beauty of compose is the same as the beauty of the Dockerfile. Portability, reproducibility (mostly), and a single readable file with all the relevant parts. It means a developer ca…

podman-compose is "mostly" compatible. I "plain" podman at work, but there we just have a bunch of shell scripts that spin up/down/build containers. For regular dev work, it's fine.

For personal stuff, I've been experimenting with podman's Kubernetes files: https://docs.podman.io/en/latest/markdown/podman-kube.1.html. Which, IMO, "feel" like docker-compose the most. You can run services via "podman kube play ..." and install them via quadlet install too.

Re: Podman v6.0.0

#230
post #192

Earlier quoted context omitted.

> 5.7.0+ds2-3build1 No thanks I'll get it from podman.

What's wrong with 5.7.0+ds2-3build1 ?

Ubuntu loves to mess with upstream by shipping a bunch of vendor patches. It's one of the main reasons I run Fedora, they do this the least in my experience
Post reply on HN