Hacker News new | ask | show | jobs
by jcastro 28 days ago
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 Universe. Everything in this thread makes sense, it's a matter of who wants to pay for it. End users have been asking for this for years.

The engineers don't make the decisions. Canonical doesn't want to pay, Red Hat doesn't want to pay. Users stuck in the middle.

I get podman from brew even on Linux because the idea that vendors fighting over uploading tarballs to a server is stupid. Fuck distros.

2 comments

I'm confused, the latest LTS version of Ubuntu is 26.04 (released on 2026/04/23) and has Podman v5.7.0 (released on 2025/11/11). [1]

If they're on a 24.04 LTS release is there any reason they would be on a newer version of Podman (without jumping through hoops)? Ubuntu 24.04LTS released on 2024/04/25 and the Debian Import Freeze was on 2024/02/29.

The bleeding edge Podman release at that time was a pre-release v5.0.0-RC3 (2024/02/22) and the latest actual release was v4.9.3 (2024/02/13). That's the version Ubuntu 24.04LTS has. [2][3][4]

So aren't they on the exact version of Podman they're supposed to be on for the operating system version they're running?

[1] https://packages.ubuntu.com/resolute/podman

[2] https://packages.ubuntu.com/noble/podman

[3] https://documentation.ubuntu.com/release-notes/24.04/schedul...

[4] https://github.com/podman-container-tools/podman/releases?pa...

> 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
Every distro does this. That's what a distro is.
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 distros is such a major cluster F.

If I manage an open source program like this, my job is to write the code and docs, publish it somewhere and maybe make some changes to make it more portable. That's it!

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.

> If RedHat doesn't choose to

You still don't get it: Canonical didn't choose to include a newer version in their 24.04 release.

24.04 is a stable release. Package updates in stable releases need to follow the Stable Release Update process https://ubuntu.com/project/docs/SRU/stable-release-updates/ In essence someone needs to do contribute time and effort to make it happen. Canonical is free to choose the packages they want to maintain themselves and which ones go to universe and are community maintained. The upstream, if they care enough, can choose to get involved and try to do the updates. The process isn't exactly easy or fun. There's a bunch of requirements regarding backward compatibility and testing that need to be met. Snapd upstream goes though it for almost every release and it takes anything from a couple of weeks to a month. I don't think anything is stopping either party from updating the packages, although I don't why upstream wouldn't be interested in getting involved making this happen.
Thank you for the explanation!