Simulate connection problems in container
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I am debugging an issue with application which connects to RabbitMQ.
So I have docker-compose file with 2 containers: my app and RebbitMQ.
I would like to see what is going on if there are serious connection problems.
My first idea was to exec
to docker container running rabbit and type:
ifconfig eth0 down
Unfortunately this is not allowed in containers and i get: Permission denied.
What other options do I have? (currently RabbitMQ is alpine-based so there are not much tools pre-installed but I can easily switch my test RabbitMQ container to another distro).
networking docker alpine-linux
add a comment |Â
up vote
0
down vote
favorite
I am debugging an issue with application which connects to RabbitMQ.
So I have docker-compose file with 2 containers: my app and RebbitMQ.
I would like to see what is going on if there are serious connection problems.
My first idea was to exec
to docker container running rabbit and type:
ifconfig eth0 down
Unfortunately this is not allowed in containers and i get: Permission denied.
What other options do I have? (currently RabbitMQ is alpine-based so there are not much tools pre-installed but I can easily switch my test RabbitMQ container to another distro).
networking docker alpine-linux
If the containers are set up with the same network group, can you not just bring down the network?
â Raman Sailopal
Feb 8 at 11:41
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am debugging an issue with application which connects to RabbitMQ.
So I have docker-compose file with 2 containers: my app and RebbitMQ.
I would like to see what is going on if there are serious connection problems.
My first idea was to exec
to docker container running rabbit and type:
ifconfig eth0 down
Unfortunately this is not allowed in containers and i get: Permission denied.
What other options do I have? (currently RabbitMQ is alpine-based so there are not much tools pre-installed but I can easily switch my test RabbitMQ container to another distro).
networking docker alpine-linux
I am debugging an issue with application which connects to RabbitMQ.
So I have docker-compose file with 2 containers: my app and RebbitMQ.
I would like to see what is going on if there are serious connection problems.
My first idea was to exec
to docker container running rabbit and type:
ifconfig eth0 down
Unfortunately this is not allowed in containers and i get: Permission denied.
What other options do I have? (currently RabbitMQ is alpine-based so there are not much tools pre-installed but I can easily switch my test RabbitMQ container to another distro).
networking docker alpine-linux
asked Feb 8 at 11:32
Derp
4202616
4202616
If the containers are set up with the same network group, can you not just bring down the network?
â Raman Sailopal
Feb 8 at 11:41
add a comment |Â
If the containers are set up with the same network group, can you not just bring down the network?
â Raman Sailopal
Feb 8 at 11:41
If the containers are set up with the same network group, can you not just bring down the network?
â Raman Sailopal
Feb 8 at 11:41
If the containers are set up with the same network group, can you not just bring down the network?
â Raman Sailopal
Feb 8 at 11:41
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
I used a special container between RabbitMQ and my app called muxy:
There are different kinds of so called "midleware" which you can add to this proxy in order to simulate different kinds of network problems.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
I used a special container between RabbitMQ and my app called muxy:
There are different kinds of so called "midleware" which you can add to this proxy in order to simulate different kinds of network problems.
add a comment |Â
up vote
0
down vote
accepted
I used a special container between RabbitMQ and my app called muxy:
There are different kinds of so called "midleware" which you can add to this proxy in order to simulate different kinds of network problems.
add a comment |Â
up vote
0
down vote
accepted
up vote
0
down vote
accepted
I used a special container between RabbitMQ and my app called muxy:
There are different kinds of so called "midleware" which you can add to this proxy in order to simulate different kinds of network problems.
I used a special container between RabbitMQ and my app called muxy:
There are different kinds of so called "midleware" which you can add to this proxy in order to simulate different kinds of network problems.
answered Feb 12 at 8:49
Derp
4202616
4202616
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f422779%2fsimulate-connection-problems-in-container%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
If the containers are set up with the same network group, can you not just bring down the network?
â Raman Sailopal
Feb 8 at 11:41