Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Add ability to throttle bandwidth by container #37
In some test cases it would be nice to see how code performs when at a limited bandwidth, for example 28k, 56k, etc. Adding this ability to docker would make running these sort of tests easier.
It would also be handy from an administrator perspective as well.
referenced this issue
Mar 16, 2014
Sorry to dig this up - but what exactly is the current best way of doing this from Docker?
Do we find the
Or we can use the cgroup system directly to set net_cls on the containers, and then apply rules to that?
Are there any plans for tighter integration of Docker with per-container bandwidth controls?
@victorhooi : there are many ways to do it. Ideally it might have to be bound to network strategies (i.e. the new feature in libcontainer that lets containers have multiple interfaces and different interface types), since one will not use the same technique to limit traffic on a veth and on a macvlan interface (even though in that case, tc will get us pretty far). I have no experience with
FYI: net_cls only sets a classid/flag on outgoing packets so that they can be identified in tc or iptables, ie. not usable to control incoming bandwidth.
On Tuesday 25 March 2014 at 07:16, Jérôme Petazzoni wrote: