-
Notifications
You must be signed in to change notification settings - Fork 1
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
Examples on how to use comcast on a specific container #1
Comments
I'm trying to do exactly this. |
Hmm, if you want to do this then you'll need to give your container Some other notes:
|
@aidanhs Thanks for your time and thoughts. Going to try again using the I will keep you guys posted :) |
I've written a bit more in tylertreat/comcast#48 (comment), but the upshot is that it seems a bit unfortunate to give random containers extra network permissions and bloat them with more dependencies. If you wanted to get serious about it, I'd build a simple REST API on top of docker-comcast and expose it as a docker service so containers can request throttling - no extra perms or dependencies in your containers. Of course, this may be a bit heavy if you just want one container to self-configure. I'll ponder on making a REST API myself and adding a technique talking about exposing it as a service in the next edition of the book - is this something people would find useful? I'm also interested whether people on this issue are readers or have found this repo some other way - either way, I'm glad people are finding it useful! |
My use case is to test a webrtc based video conferencing application, with comcast I am able to do throttling of UDP packets for my whole system, but what I want is to have different network conditions for each app instance. I want to see how my application behaves when one of the participant's network is unstable, with comcast all participant's network is throttled because of how it works. If I could containerize, I can fulfill my use case. |
Would it be possible to run this from within the container that you want to throttle? That way the network throttling is handled by the container itself?
The text was updated successfully, but these errors were encountered: