Live data from Hacker News

I ditched Docker for Podman

codesmash.dev

371–380 of 670 posts

Re: I ditched Docker for Podman

#371

Earlier quoted context omitted.

> What else can they do... They can do what Docker and many other software providers do that are committed to cross OS functionality. They could build packages for those OSes. Example: https://docs.docker.com/engine/install/ubuntu/#install-using... The install instructions you link to are relying on the OS providers to build/package Podman as part of their OS release process. But that is notoriously out-of-date. You…

> build/package Podman as part of their OS release process. But that is notoriously out-of-date. providing duplicate/additional non official builds for other OS is - undermining the OSes package curation - confusing for the user - cost additional developer time, which for most OSS is fairly limited - for non vendorable system dependencies this additional dev time cost can be way higher in all kinds of surprising ways…

> cost additional developer time, which for most OSS is fairly limited

Mostly agree. But something like Podman w/ RedHat behind it is unlikely to be limited in the same way a lot of community OSS projects are.

Unfortunately, I disagree with just about every other point you made but don't think it's worth responding point-by-point. In short, I think a project having dedicated builds for popular OSes is a win-win for just about everyone, excepting that it does take, sometimes a considerable amount of, effort to support those cross OS builds. Additionally, there are now options like Snap/Flatpack/AppImage that can be targets instead of the OS itself, although there is admittedly a tradeoff there as well.

For some projects, say something like ripgrep, just using what is in the OS repo is fine because having the latest and greatest features/bug-fixes is unlikely to matter to most people using the tool.

But, on something like Podman, where there is so many pieces, it's a relatively new technology, and the interaction between Kernel, OS, and user space is so high, being stuck with a non-current OS provided release for a couple years is a non-starter.

> why not use a Linux distribution which works with modern software development cycles?

Because I like my OS to be stable, widely supported, and I also like some of my applications to be evergreen. I find Ubuntu is usually a really good mix that way and I'm going on 15+ years of use. There are other solutions for that that I could use, but I'm mostly happy where I am and don't want to spend the kind of time it would take to adopt a different OS and everything that would follow from that.

That leads _me_ to avoid Podman currently. I can appreciate that you have a different opinion, I just think you are a overplaying your perspective a bit in the comment above.

Re: I ditched Docker for Podman

#372

Earlier quoted context omitted.

This is what Lima is, which is the basis for Colima which runs on top with all the Docker runtime stuff https://github.com/lima-vm/lima https://github.com/abiosoft/colima

Interesting, thanks. Looks much better than Docker/Podman. But seems to suffer from the same incentive issue. I think I'll stick with my raw QEMU setup, Lima seems like QEMU + batteries, but I already built the batteries.

Fun fact podman desktop is just a front end to Lima, or was last I checked

Re: I ditched Docker for Podman

#373

Earlier quoted context omitted.

I don't understand why people need a gui for docker/podman.

I use orbstack, but I never look at it, it just opens when I start up the computer. I used to use docker desktop, which I never looked at either. The docker daemon has always just been broken on Mac for as long as I've been trying to work with it (about 4 years, at least as far as Mac environments). Idk what the problem is, but it's ugly. I switched to orbstack because there was something like a memory leak happening…

On Windows, the easiest thing is to just use podman without podman desktop. It installs easily as a winget package and works in your current shell without having to first start WSL (it does that behind the scenes).

On Linux, for development, podman and docker are pretty similar but I prefer the k8s yaml approach vs compose so tend to use podman.

I don't think Apple really cares about dev use cases anymore so I haven't used a Mac for development in a while (I would for iOS development of course if that ever came up).

Re: I ditched Docker for Podman

#374
post #209

Earlier quoted context omitted.

Is linking to a 404 page meant to highlight the lack of docs, or is there some mistake?

Apparently the documentation was just updated. The new location is https://docs.podman.io/en/latest/markdown/podman-quadlet.7.h...

You can also look the documentation up locally: `man quadlet`

Re: I ditched Docker for Podman

#375
> just convert it to Kubernetes YAML

Either you haven't worked on k8s at scale or you're seriously suggesting an overly complex solution to elegant docker-compose. Docker compose exists because of it's simplicity and stability. I have also started using swarm and it doesn't get the recognition it deserves for the most easy-to-manage orchestration. Podman doesn't have such a thing. And yes, podman-compose is absolute garbage

Re: I ditched Docker for Podman

#376
post #143
post #46

Earlier quoted context omitted.

> On the plus side, any company I work for doesn't have to worry about licences. Win win! Was this a deal breaker for any company? I ask because the Docker Desktop paid license requirement is quite reasonable. If you have less than 250 employees and make less than $10 million in annual revenue it's free. If you have a dev team of 10 people and are extremely profitable to where you need licenses you'd end up paying $9…

Docker Desktop is also (imo) useless and helps be ignorant. Most Mac users I see using it struggle to see the difference between "image" and "container". Complete lack of understanding. All the same stuff can easily be done from cli.

[deleted]

Re: I ditched Docker for Podman

#378
post #46
post #21

To provide 1 contrary opinion to all the others saying they have a problem: Podman rocks for me! I find docker hard to use and full of pitfalls and podman isn't any worse. On the plus side, any company I work for doesn't have to worry about licences. Win win!

> On the plus side, any company I work for doesn't have to worry about licences. Win win! Was this a deal breaker for any company? I ask because the Docker Desktop paid license requirement is quite reasonable. If you have less than 250 employees and make less than $10 million in annual revenue it's free. If you have a dev team of 10 people and are extremely profitable to where you need licenses you'd end up paying $9…

> you'd end up paying $9 a year per developer for the license

It's only 9 bucks a year, its only 5 bucks a month, its less than a dollar a day.

Docker, ide, ticking system, GitHub, jira, sales force, email, office suit, Figma.... all of a sudden your spending 1000 bucks a month per staff member for a small 10 person office.

Meanwhile AWS is charging you .01xxxx for bandwidth, disk space, cpu time, s3 buckets, databases. All so tiencent based AI clients from China hammer your hardware and run up your bill....

The rent seeking has gotten out of hand.

Re: I ditched Docker for Podman

#379
post #209

Earlier quoted context omitted.

Apparently the documentation was just updated. The new location is https://docs.podman.io/en/latest/markdown/podman-quadlet.7.h...

I do believe you about the "updated" part, and that's a constant hazard with linking to "latest" or "main" of anything. But I don't know why you'd then change the actual file in the URL, since the original comment was citing "podman-systemd.unit.5.html" https://docs.podman.io/en/v5.6.1/markdown/podman-systemd.uni... > and you've chosen to cite quadlet.7

Not OP but "podman-systemd.unit.5" used to be the primary Quadlet documentation (a remnant of when it was podman-generate-systemd perhaps?) with every Quadlet file type (.container, .volume, .network, etwc) documented on one page.

The new docs split that out into separate podman-container/volume/etc.unit(5) pages, with quadlet.7 being the index page. So they're still linking to the same documentation, just the organization happened to change underneath them.

If you must see what they linked to originally, the versions docs are still the original organization (i.e. all on one page): https://docs.podman.io/en/v5.6.0/markdown/podman-systemd.uni...

Re: I ditched Docker for Podman

#380
I ditched Docker and Podman for FreeBSD Jails :)

More here:

- https://vermaden.wordpress.com/2023/06/28/freebsd-jails-cont...

- https://vermaden.wordpress.com/2025/04/11/freebsd-jails-secu...

- https://vermaden.wordpress.com/2025/04/08/are-freebsd-jails-...

- https://vermaden.wordpress.com/2024/11/22/new-jless-freebsd-...

Post reply on HN