-
Notifications
You must be signed in to change notification settings - Fork 18.7k
Add ability to throttle bandwidth by container #37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
best done with TC? but then you need a new bridge for each container.. |
I'm not 100% sure, but I think that Another possibility is to use |
oh, apparently, with cgroup net_cls you can classify traffic from/to each container and let tc shape that class, no need for multiple bridges.. |
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:
|
…atching [18.09] backport: fix regression when filtering container names using a leading slash
Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
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.
The text was updated successfully, but these errors were encountered: