crun
Ranked 14 of 14 container runtimes by recommenders
People recommend crun as a good-enough container runtime that the Linux community commonly uses. Critics say its defaults enable namespace-incompatible security features.
People recommend crun as a good-enough container runtime that the Linux community commonly uses. Critics say its defaults enable namespace-incompatible security features.
8 people gave an opinion
- recommend it
- 5
- criticize it
- 3
- approval share
- 63%
Recommended in 3 of 13 months
- November 2025: not recommended
- December 2025: not recommended
- January 2026: recommended
- February 2026: not recommended
- March 2026: not recommended
- April 2026: not recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 5 people recommend itNeeds 10 or more, not met.
- 1.6 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 3 of 13 monthsNeeds 4 or more, not 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
Good enough for containers
“crun has just proven good enough”
Comment from 23 Oct 2026 in “Docker is weird” Common Linux community solution
“the Linux community general solved via crun”
Comment from 14 Jul 2026 in “Grok uploaded my user directory to xAI's servers”
What people warn about
Each mark is one comment
Defaults enable namespace-incompatible features
“Crun just stamp couples security profiles as an example, so everything in the shared kernel that is namespace incompatible is enabled.”
Comment from 23 Jan 2026 in “What Has Docker Become?” “if crun set reasonable defaults and restricted namespace incompatible features by default we would be in a better position”
Comment from 13 Jan 2026 in “Signal leaders warn agentic AI is an insecure, unreliable surveillance risk” “Crun just stamp couples security profiles as an example”
Comment from 23 Jan 2026 in “What Has Docker Become?” Runtime quirks differ from runc
“runtime quirks between runc and crun”
Comment from 8 Mar 2026 in “A Decade of Docker Containers”
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 |
| crunThis page | 5 | 3 | 63% | 3 | — | — |
What people said
6 of the 8 comments that mention it, newest first. Each links to the original comment.
“crun has just proven good enough”
“the Linux community general solved via crun”
“runtime quirks between runc and crun”
“Crun just stamp couples security profiles as an example”
“Crun just stamp couples security profiles as an example, so everything in the shared kernel that is namespace incompatible is enabled.”
“if crun set reasonable defaults and restricted namespace incompatible features by default we would be in a better position”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.