Loading content
Linux Containers (LXC) are an OS-level virtualization technology on Linux that provides isolated user environments using namespaces and cgroups. They enable lightweight containers with lower overhead compared to full VM virtualization. LXC is used for hosting, multi-tenant workloads, and developer sandboxes. Administrators must configure security profiles an…
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
Linux Containers (LXC) is operating-system virtualization that runs multiple isolated Linux environments on a host while sharing its kernel.
LXC grew from the problem of isolating processes with Linux kernel mechanisms such as namespaces and cgroups. The Linux Containers project assembled these primitives into tools and libraries for system containers; LXD later emerged as a complementary management ecosystem.
A container here has no separate kernel: the host kernel provides namespaces for visibility and cgroups for resources. LXC assembles a filesystem, processes, network, and limits so the container feels like a small Linux system while sharing the host kernel.
It isolates which processes, networks, or mounts a container can see.
It limits and measures resources such as CPU or memory.
It supplies the files and tools of the isolated environment.
LXC fits lightweight, system-level environments, test systems, and tenant separation on Linux hosts. Shared-kernel operation makes host security, privileges, images, and kernel compatibility important operational concerns.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.