[$] Containers as a recognized kernel object
The foundation of the design for containers in the kernel is that there isn't one; there is no container abstraction that the kernel recognizes.
Why am I seeing this Ranked on source trust — LWN
It ranks mainly on source trust: LWN is the most reliable outlet we track on this subject, and is the only one on the story so far.
Single-sourced. No second organisation has confirmed it yet.
Link-outLink-out, because only one organisation carries it and no first-party source is on it and the subject could not be identified from the text. Link-out means we point at the publisher and say nothing of our own.
| Factor | Weight | Score | Contribution | Where it came from |
|---|---|---|---|---|
| Corroboration | 0.35 | 0.39 | +0.135 31% | 1 independent org on the story. Tier-3 aggregators never corroborate — they can show something is circulating, never that it is true. |
| Source trustleads | 0.25 | 0.85 | +0.212 49% | LWN is the highest-trust source on this story. Trust is taken from the best source, not averaged. |
| Pickup rate | 0.20 | 0.00 | +0.000 0% | One counted organisation, so there is no spread to measure — nothing has picked this up to set a rate. |
| Freshness | 0.20 | 0.43 | +0.086 20% | Halves every 10 hours from the newest item on the story. This is the only factor that rewards a story for nothing more than being recent. |
Corroboration counts distinct organisations, once each, and only from tiers 1 and 2. Freshness halves every 10 hours, so this ranking is a snapshot and will differ at the next build.
Kuzux · CC BY-SA 2.5 · Wikimedia Commons · illustrativeJosef Bacik is proposing a kernel-level abstraction for containers called "cells," marking a new attempt to give containers formal recognition in the kernel. Currently, the kernel treats containers as a collection of separate components—namespaces, control groups, and sandboxing mechanisms—rather than as unified objects. Previous efforts to establish containers as first-class kernel objects have not succeeded.
The cells proposal would change how the kernel handles container functionality by consolidating these disparate mechanisms into a recognized abstraction. This differs from the existing approach where developers must manually combine kernel features to build container support. If accepted, the change would represent a significant shift in kernel architecture.
The proposal faces the challenge of prior failed attempts to standardize container support at the kernel level. Whether cells will succeed where previous efforts did not remains to be determined. The concept is currently in early stages of development.
What happened
The foundation of the design for containers in the kernel is that there isn't one; there is no container abstraction that the kernel recognizes. Instead, the kernel provides a long list of components — namespaces, control groups, sandboxing mechanisms, and more — along with a note that says, in effect, "some assembly required". There have been attempts ( repeatedly ) over the years to turn containers into first-class objects with kernel support, but they have never gotten far. Now Josef Bacik is making a try with a concept that he calls "cells".
How this story arrived
Ordered by when each source was first observed, which is what the velocity figure is computed from. Publishers backdate; observed order does not.
- 01 Lwn first seen [$] Containers as a recognized kernel object
Overclock clusters coverage from independent sources and grades it automatically. The figures above are computed, not editorial. This page summarises and links to reporting by the outlets named — follow the links for the original work.