Podman
Hacker ApprovedThe most recommended of 14 container runtimes
A daemonless, rootless-by-default Docker alternative with systemd and Kubernetes-style pod integration; expect occasional Docker incompatibilities and extra setup work.
A daemonless, rootless-by-default Docker alternative with systemd and Kubernetes-style pod integration; expect occasional Docker incompatibilities and extra setup work.
369 people gave an opinion
- recommend it
- 276
- criticize it
- 93
- approval share
- 75%
Recommended in 12 of 13 months
- November 2025: recommended
- December 2025: recommended
- January 2026: recommended
- February 2026: recommended
- March 2026: recommended
- April 2026: recommended
- May 2026: recommended
- June 2026: recommended
- July 2026: recommended
- August 2026: recommended
- September 2026: recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Owned for 1.5 years
Median of the 21 owners who said how long they have had it.
Each square is one year.
Why it carries the badge
- 276 people recommend itNeeds 10 or more, met.
- 3 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 12 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Rootless and more secure
“Rootless was the reason I switched to Podman years ago. It's just so smooth and I don't have to worry about obscure permissions and services errors anymore.”
Comment from 2 Jul 2026 in “Podman v6.0.0” “Rootless Podman forces you to think about permissions and does not stab you in the back by overwriting your firewall rules.”
Comment from 3 Jul 2026 in “Podman v6.0.0” “Podman is a different product that is pretty much a drop-in replacement for Docker but lets you run as non-root.”
Comment from 23 Jan 2026 in “What Has Docker Become?” - Comment from 18 Jun 2026 in “A Modern Proxmox Docker Architecture with Disposable VMs, VirtIO-FS, and ZFS”
- Comment from 17 Sep 2026 in “Backups Aren't Simple”
- Comment from 22 Dec 2025 in “Lotusbail npm package found to be harvesting WhatsApp messages and contacts”
- Comment from 20 Sep 2026 in “Custom home server built from spare parts”
Mostly drop-in Docker replacement
“I use podman regularly, and despite it being a good drop-in replacement like 95% of the time, the 5% of the time where it isn't seamless are super painful”
Comment from 2 Jul 2026 in “Podman v6.0.0” “Highly recommend Podman overall; there are some quirky edge cases, but for the most part it's a smooth replacement for Docker.”
Comment from 2 Jul 2026 in “Podman v6.0.0” “Podman is a different product that is pretty much a drop-in replacement for Docker but lets you run as non-root.”
Comment from 23 Jan 2026 in “What Has Docker Become?” - Comment from 18 Dec 2025 in “A Safer Container Ecosystem with Docker: Free Docker Hardened Images”
- Comment from 5 May 2026 in “Should I Run Plain Docker Compose in Production in 2026?”
Systemd and Quadlet integration
“It was worthwhile as I can just use my usual systemctl and journalctl utilities for both containerized and non-containerized services”
Comment from 3 Jul 2026 in “Podman v6.0.0” “Podman has supported plugin compose (v2) for years now, and I believe that's the version I used before I switched to Quadlets”
Comment from 3 Jul 2026 in “Podman v6.0.0” “The easiest way to do this is by using system-level Podman Quadlets that run as an unprivileged user account.”
Comment from 29 Aug 2026 in “AI Agent Has Root” Kubernetes-style pods
“It provides similar functionality as docker-compose, using a yaml file which is a subset of the Kubernetes pod definition syntax.”
Comment from 23 Jan 2026 in “What Has Docker Become?” “podman supports it natively and you can actually wrap your app containers into a single "pod" for easier management”
Comment from 3 Jul 2026 in “Podman v6.0.0” “the biggest advantage of podman is that it uses pods with basically the same config and behavior as kubernetes does”
Comment from 8 Sep 2026 in “Be Using Rootless Containers”
What people warn about
Each mark is one comment
Docker incompatibilities and edge cases
“I use podman regularly, and despite it being a good drop-in replacement like 95% of the time, the 5% of the time where it isn't seamless are super painful”
Comment from 2 Jul 2026 in “Podman v6.0.0” “podman is not a drop-in replacement for Docker. You can replace it with podman but expect to encounter minor inconsistencies and some major differences”
Comment from 18 Dec 2025 in “I got hacked: My Hetzner server started mining Monero” “I have found this to be perennially true. I am willing to doggedly pursue the root cause and file bugs, but for many people it will just seem broken.”
Comment from 2 Jul 2026 in “Podman v6.0.0” - Comment from 2 Jul 2026 in “Podman v6.0.0”
- Comment from 2 Jul 2026 in “Podman v6.0.0”
Harder to set up than Docker
“It’s the setting up systemd unit files and local user accounts for rootless / daemonless deployment of containerized apps that can be a headache.”
Comment from 2 Jul 2026 in “Podman v6.0.0” “Podman requires a bit of extra work to implement well and that is just enough of an annoyance to tip the scales towards Docker.”
Comment from 2 Jul 2026 in “Podman v6.0.0” “I think Podman is better in a number of ways, but it isn’t the most intuitive to implement compared to Docker.”
Comment from 2 Jul 2026 in “Podman v6.0.0” Compose support friction
“If you're using docker-compose.yml on a team that mostly uses docker, you can't use use that same docker-compose.yml with rootless podman.”
Comment from 2 Jul 2026 in “Podman v6.0.0” “Podmans solution is to not commit to compose, but instead to create a bespoke mechanism involving a bunch of tiny files”
Comment from 2 Jul 2026 in “Podman v6.0.0” Platform support issues
“Luckily Podman seems to support FreeBSD these days for docker images, but the Linux emualation might be a bit of a blocker”
Comment from 22 Feb 2026 in “Back to FreeBSD: Part 1” “Podman had some issues with WSL 3 that they're still releasing fixes for, but it's all working with that too.”
Comment from 15 Oct 2026 in “What I self-host” “They put rootless as a forefront before it was ready and still no proper support for Ubuntu on v4 of Podman.”
Comment from 2 Jul 2026 in “Podman v6.0.0”
Other container runtimes people recommend
The four most recommended other container runtimes, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Podman | 276 | 93 | 75% | 12 | 1.5 yrs21 owners | Approved |
| OrbStack | 97 | 11 | 90% | 12 | 2 yrs3 owners | Approved |
| Apple container | 56 | 28 | 67% | 11 | — | Approved |
| gVisor | 45 | 16 | 74% | 12 | — | Approved |
| Colima | 39 | 8 | 83% | 11 | — | Approved |
What people said
40 of the 501 comments that mention it, newest first. Each links to the original comment.
“Podman had some issues with WSL 3 that they're still releasing fixes for, but it's all working with that too.”
“It is far more secure by design (rootless) and is unable to silently alter the firewall's configuration.”
“The ideal setup is rootless Podman and having all your containers not even be able to create root-owned files.”
“the biggest advantage of podman is that it uses pods with basically the same config and behavior as kubernetes does”
“The easiest way to do this is by using system-level Podman Quadlets that run as an unprivileged user account.”
“This allows rootful Podman to orchestrate privileged capabilities while running the container processes in an unprivileged namespace.”
“Podman now follows the UAPI Configuration Files Specification as well as the Base Directory Specification. This is great!”
“podman supports it natively and you can actually wrap your app containers into a single "pod" for easier management”
“Podman has supported plugin compose (v2) for years now, and I believe that's the version I used before I switched to Quadlets”
“Rootless Podman forces you to think about permissions and does not stab you in the back by overwriting your firewall rules.”
“It was worthwhile as I can just use my usual systemctl and journalctl utilities for both containerized and non-containerized services”
“Podman requires a bit of extra work to implement well and that is just enough of an annoyance to tip the scales towards Docker.”
“I think Podman is better in a number of ways, but it isn’t the most intuitive to implement compared to Docker.”
“We have a consistent wsl image for everyone. So they are all on Linux. Then we have a podman pod defined in a bash script.”
“Podmans solution is to not commit to compose, but instead to create a bespoke mechanism involving a bunch of tiny files”
“It put me off Podman for years. I do now think it has some clever ideas and if you're running RHEL it's a no brainer”
“I use podman regularly, and despite it being a good drop-in replacement like 95% of the time, the 5% of the time where it isn't seamless are super painful”
“It’s the setting up systemd unit files and local user accounts for rootless / daemonless deployment of containerized apps that can be a headache.”
“They put rootless as a forefront before it was ready and still no proper support for Ubuntu on v4 of Podman.”
“I have found this to be perennially true. I am willing to doggedly pursue the root cause and file bugs, but for many people it will just seem broken.”
“most of the fixes for Podman/Docker incompatibilities is just addressing that assumption with a few extra flags”
“If you're using docker-compose.yml on a team that mostly uses docker, you can't use use that same docker-compose.yml with rootless podman.”
“Rootless was the reason I switched to Podman years ago. It's just so smooth and I don't have to worry about obscure permissions and services errors anymore.”
“Highly recommend Podman overall; there are some quirky edge cases, but for the most part it's a smooth replacement for Docker.”
“Podman comes with no socket and rootless by default, it just seems more in line with this sort of architecture”
“the exploit failed. I am not sure if the default container runtime in Podman is resistant against these attacks”
“activate Podman's Docker API compatibility socket, and simply set your DOCKER_HOST env var to that socket”
“if you already know how to use docker/podman and just want to get something working in an evening, this works too”
“I've been experimenting with the immutable fedora-bootc images and podman+Containerfiles, which works pretty well for this.”
“Podman is a viable option. I'm not sure how it works but I was able to run Alpine and Debian containers by setting a few system flags.”
“Luckily Podman seems to support FreeBSD these days for docker images, but the Linux emualation might be a bit of a blocker”
“podman quadlet doesn't seem to support running at a "system level" as a non-root user, at least according to their docs”
“Podman is a different product that is pretty much a drop-in replacement for Docker but lets you run as non-root.”
“It provides similar functionality as docker-compose, using a yaml file which is a subset of the Kubernetes pod definition syntax.”
“of course I don't mount my entire harddrive to the container when it's running, that would defeat the entire purpose.”
“Easiest for now is just run everything in rootless podman containers (or similar), which is relatively easy.”
“Podman already supports PTYs that can be attached/detached, allows isolating different processes, and has an HTTP API.”
“podman is not a drop-in replacement for Docker. You can replace it with podman but expect to encounter minor inconsistencies and some major differences”
“Instead, activate Podman's Docker API compatibility socket, and simply set your DOCKER_HOST env var to that”
“The CI/CD pipeline triggers a podman auto-update command, and just like that all containers are running the latest version.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.