Use Docker containers as hosts inside your Mininet topologies. Interact with the containers through Mininet's CLI.
This fork of Mininet allows to use Docker containers as Mininet hosts. This enables interesting functionalities to built networking/cloud testbeds. The integration is done by subclassing the original Host class.
Based on: Mininet 2.2.1
- Contributions welcome :-)
Cite this work
If you use Containernet for your research and/or other publications, please cite the following paper to reference our work:
- Manuel Peuster, Holger Karl, and Steven van Rossem. "MeDICINE: Rapid Prototyping of Production-Ready Network Services in Multi-PoP Environments." to appear in IEEE Conference on Network Function Virtualization and Software Defined Network (NFV-SDN), 2016.
- Pre-print online: http://arxiv.org/abs/1606.05995
- Add, remove Docker containers to Mininet topologies
- Connect Docker containers to topology (to switches, other containers, or legacy Mininet hosts )
- Execute commands inside Docker containers by using the Mininet CLI
- Dynamic topology changes (lets behave like a small cloud ;-) )
- Add Hosts/Docker containers to a running Mininet topology
- Connect Hosts/Docker containers to a running Mininet topology
- Remove Hosts/Docker containers/Links from a running Mininet topology
- Resource limitation of Docker containers
- CPU limitation with Docker CPU share option
- CPU limitation with Docker CFS period/quota options
- Memory/swap limitation
- UPDATE CPU/Mem limitations at runtime!
- Traffic control links (delay, bw, loss, jitter)
- (missing: TCLink support for dynamically added containers/hosts)
- Automated unit tests for all new features
- Automated installation based on Ansible playbook
- Ubuntu 14.04 LTS
Automatic installation is provide through an Ansible playbook.
- Requires: Ubuntu 14.04 LTS
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install ansible git aptitude
sudo vim /etc/ansible/hosts
git clone https://github.com/mpeuster/containernet.git
sudo ansible-playbook install.yml
- Wait (and have a coffee) ...
Usage / Run
Start example topology with some empty Docker containers connected to the network.
sudo python examples/dockerhosts.py
containernet> d1 ifconfigto see config of container d1
There is a set of Containernet specific unit tests located in
mininet/test/test_containernet.py. To run these, do:
sudo py.test -v mininet/test/test_containernet.py
cd bin/; sudo clear_crash.shto cleanup the environment after something went wrong.
Using the provided Vagrantfile is the most simple way to run and test Containernet.
git clone https://github.com/mpeuster/containernet.git cd containernet vagrant up vagrant ssh
And follow the instructions in the MOTD message.
Containernet can be executed within a container itself. This results in a containers-inside-container setup and simplifies its distribution.
A pre-build image is also available on Docker Hub (auto build of latest code revision on GitHub):
To run the Containernet Docker image:
docker run -ti --rm=true --net=host --pid=host --privileged=true -v '/var/run/docker.sock:/var/run/docker.sock' mpeuster/containernet
To build the Containernet Docker image:
docker build -t containernet .
HINT: If you are using docker-machine on OS X, you have to execute the following before you can run Containernet inside a Docker container.
docker-machine ssh default "sudo modprobe openvswitch"
Containernet (c) 2015 by Manuel Peuster
manuel (dot) peuster (at) upb (dot) de