Replies: 2 comments 3 replies
-
|
How would wings enforce this quota? just shut the server down? Docker does not support speed limits nor network data limits. |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
Duplicate of #1473 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
It would be great to be able to set how much bandwidth (for example, how many GB of internet traffic) a specific server [container] is allowed to transfer in download and upload over a defined period of time.
For example, a bandwidth limit that automatically resets every 7 days, 30 days, or any custom interval.
One possible approach could be to identify the container by its name (which I noticed remains constant, since it corresponds to the server’s UUID), and then apply traffic limits using something like nftables quotas, combined with a Docker container IP lookup (so the container can be resolved via its name/UUID to the correct IP)? And so when limit reached...just like dropping incoming and outgoing traffic for the container specific ip/interface.
This logic could then be managed by Wings, which would be responsible for tracking usage, enforcing the quota, and resetting it when the time window expires (or for the reset maybe a cronjob?).
If I were to try implementing something like this, would that be acceptable (if good after review)? And, if so, could I open a merge request to propose it upstream?
It’s just an idea, but it could be a useful feature for controlling and fairly distributing network usage across containers & preventing abuse (making network-related abuse, like users hosting DDoS tools, harder & less efficent).
Beta Was this translation helpful? Give feedback.
All reactions