-
Notifications
You must be signed in to change notification settings - Fork 196
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
pumba netem command with docker network not working #137
Comments
@sayankc I will check it. |
hi @alexei-led , |
Hi @alexei-led , |
Hi @sayankc |
@sayankc does it work now? can I close the issue? |
@alexei-led , Issue is still there. I'll give you ifconfig. |
I've the same issue.
|
Has there been a solution to this? My own setup didn't work, but neither did the demo here: My setup is running inside windows10 wsl2.
then using No delay is applied |
Hi ,
My requirement is to create a docker container within a specific docker network and apply network chaos only on that network, so that other applications running on the host is not impacted.
Here is what I have done. But the delay is not working. only working with
--interface eth0
.create a docker network.
docker network create -d bridge --subnet 172.25.0.0/16 isolated_nw44
Run a docker container in this network.
docker run -d -p 4444:4444 -v /dev/shm:/dev/shm --name=container44 --network=isolated_nw44 --ip=172.25.3.3 selenium/standalone-chrome
check the network interface created, where the docker container is.
ip addr | grep 172.25
==> inet 172.25.0.1/16 scope global br-72aff75d4744Now applying netem on the new interface (br-72aff75d4744)
./pumba_linux_amd64.v0.6.5 netem --duration 5m --interface br-72aff75d4744 --tc-image gaiadocker/iproute2 delay --time 1000 container44
Result : It is not resulting any additional delay for the URL(
http://ipadderss-of-host:4444/
)./pumba_linux_amd64.v0.6.5 netem --duration 5m --interface eth0 --tc-image gaiadocker/iproute2 delay --time 1000 container44
The text was updated successfully, but these errors were encountered: