Podman v6.0.0

soheilpro 454 points 180 comments July 02, 2026
blog.podman.io · View on Hacker News

Discussion Highlights (20 comments)

mjburgess

Sanctuary! mercy from grey font

alessandroberna

I love the naming of their new networking tools. Now there's pesto to go along with pasta

SwellJoe

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.

roger_

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.

jimmar

Quadlets and rootless containers are two major reasons I'll be switching from Docker to Podman.

jdoe1337halo

I'd love to switch to Podman but I use Coolify for all of my deployments and it is Docker based, so I am kind of locked into that ecosystem for now

audidude

Does it still completely screw up file/group owners in user containers? Because they keep saying it gets fixed and then that 1 out of 10 times it's not.

Tepix

I like Podman, but what's up with that grey text colour? It looks ugly and the contrast of 4.96:1 makes it hard to read (does not reach WCAG AAA level).

mati365

I really love Quadlet. I used to host my rootless containers on Hetzner, Ansible, SystemD and RockyLinux for years without any issues and extracted it to template repo [1]. [1] https://github.com/Mati365/hetzner-podman-bunjs-deploy

PufPufPuf

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.

satvikpendem

How is Podman these days? I use OrbStack on macOS and it seems to be much faster, not sure how everything will shake out now that macOS 27 is adding (more) native and performant Linux containers, similar to WSL with micro-VMs.

cdmckay

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.

lorbus

single-file quadlets go

buredoranna

Top of my list as to why I prefer podman... no "container root" / "docker group" = "host root" shenanigans podman doesn't spew garbage and punch holes in my firewall (iptables) (edit: formatting)

himata4113

Does anyone have experience with using podman image builds for cri runtimes other than docker? If I build an image with podman will it run in cri-o, docker and other misc runtimes? Been debating on using rootless podman for building images since docker build requires sudo and it gets annoying with agentic workflows.

muti

Cool, been running my home server on podman + quadlets for about two years now and picked up a couple of things in the release notes podman quadlet list Added in v5.6.0, lists quadlets and their containers podman system migrate --migrate-db Flag added in v5.8.0. I remember seeing the bolt db deprecation warnings in the past but there was no tool to do the migration to sqlite, now there is (or just upgrade to podman 6.0.0 and it will do it automatically)

a_t48

If any Podman engineers are here: does the new /libpod/local/artifacts/add endpoint let me ingest individual layers? I have an alternative pull client that's currently a little hamstrung on Podman compared to docker+containerd, due to having to convert the entire image to tarball to ingest rather than only new layers.

LinXitoW

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 can use the same compose file locally that's used for deployment. How do people actually work with podman? Do you work with a team? How do you setup a local development stack the way you would with compose?

rsyring

As long as they refuse to support installing on Ubuntu (and other popular distros), without relying on the distro repos which are always out of date, they will continue to lose to Docker. Any serious project in this space supports as many distros as possible. It's OSS, so I'm not complaining per se, I have no right to. They owe me nothing. But this one issue has kept me from seriously considering Podman for years. They don't care about my use case and I therefore don't care to use their project. When getting the latest version looks like this[1], who is really going to consider this for serious production uses? 1: https://github.com/podman-container-tools/podman/discussions...

thewisenerd

podman's been great for me on macOS for testing stuff quick; which earlier used to need a whole limactl[3]/virt thing. you can set it up with qemu-user-static for --platform linux/amd64; i don't remember which i exactly used, or if official docs have been updated for it but looked something like [1] there is one sneaky bug in qemu that breaks uv [2] for cross-platform targets so i keep having to fall back to lima for that, but great otherwise. [1]: https://www.itix.fr/blog/qemu-user-static-with-podman/ [2]: https://github.com/astral-sh/uv/issues/16024 , https://gitlab.com/qemu-project/qemu/-/work_items/3130 [3]: https://lima-vm.io/

Semantic search powered by Rivestack pgvector
14,015 stories · 131,331 chunks indexed