Google's open-source Linux application container stack providing resource isolation through a high-level API.
lmctfy is Google's open-source Linux container stack that provides application containers for resource isolation on a single machine. It solves the problem of multiple applications competing for system resources by giving each the impression of running exclusively on the machine. The project offers both a C++ library and CLI for container management.
System administrators and developers working with Linux containers who need fine-grained resource isolation and management capabilities, particularly those interested in Google's approach to containerization.
Developers choose lmctfy for its direct lineage from Google's production container stack, its hierarchical container model with delegation capabilities, and its focus on user intent through a high-level API rather than low-level kernel interactions.
lmctfy is the open source version of Google’s container stack, which provides Linux application containers.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports nested containers with a filesystem-like naming system, enabling parent containers to delegate management to child containers, as described in the container names section.
Abstracts container management around user intent through both C++ library and CLI interfaces, focusing on what users need rather than low-level kernel details.
Derived from Google's internal container stack, offering insights into scalable resource isolation and management techniques used in large-scale environments.
Allows creation of heavily isolated containers that appear as independent hosts, useful for stringent resource separation scenarios.
Google has halted active development and is migrating to libcontainer, making lmctfy unsuitable for new or ongoing projects needing future updates.
Currently only provides isolation for CPU and memory, with key features like disk IO and network isolation still unimplemented, as noted in the roadmap.
Requires Ubuntu 12.04+ with specific kernels and dependencies, and manual cgroup mounting during initialization, increasing setup overhead and limiting portability.