A Mininet fork that enables Docker containers as emulated hosts for network and cloud emulation testbeds.
Containernet is a network emulation platform that forks Mininet to support Docker containers as emulated hosts. It solves the need for realistic, container-based network testbeds in research areas like NFV, cloud computing, and edge computing by allowing dynamic topology changes and resource-limited container integration.
Network researchers, cloud computing engineers, and developers working on NFV, SDN, or edge computing projects who require emulated environments for prototyping and testing.
Developers choose Containernet for its seamless integration of Docker with Mininet, enabling flexible, scalable emulation with real container isolation and dynamic topology management, which is essential for modern network service validation.
Mininet fork adding support for container-based (e.g. Docker) emulated hosts.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Integrates Docker containers as emulated hosts, enabling realistic isolation and easy use of existing container images, as shown in the client-server example with custom Dockerfiles.
Allows adding, removing, and connecting containers and links at runtime without restarting the emulation, crucial for flexible prototyping in NFV and edge computing scenarios.
Supports setting and adjusting CPU, memory, and swap limits on containers dynamically, essential for testing resource-constrained environments like edge nodes.
Configures link characteristics such as delay, bandwidth, loss, and jitter, enabling detailed network performance testing for research and development.
Requires Ansible, specific Ubuntu versions, and virtual environments, with documented issues on Ubuntu 24.04 due to setuptools problems, making setup cumbersome.
When run inside Docker, key features like CPU share limits are unsupported, reducing its utility for accurate resource testing in containerized environments.
Needs sudo privileges to run topologies, which introduces security risks and complicates deployment in restricted or automated CI/CD pipelines.