giteng

Thank you @xcaspar! I will try it out and get back to you.

I am facing the following error when I try to run the blade command with the container name and pid 1. Command: **./blade create cri jvm cpufullload --chaosblade-release ~/chaosblade-1.5.0-linux-amd64.tar.gz --container-name...

Solved by running the command in sudo by entering sudo -i. When I execute **docker** **run**, I am not able to destroy the **Delay** experiment. I tried "./blade d "...

I will try this out. When you say outside the container, you mean outside the Chaosblade container right? I only pulled ChaosBlade image into Docker. I didn't insert ChaosBlade into...

Ok thank you. I was able to inject cpu load in my containers. I downloaded chaosblade-tool exe (v1.3.0) and it worked. Would it be the same command? Or was this...

Thank you for your help, @xcaspar ! Almost everything works. One other question: I ran this command to run Chaosblade in its own container and it works: 1) To run...

Thank you @xcaspar ! It worked. Just one last question - So I am able to run the below command for my existing container: **docker exec -it chaosblade /bin/sh -c...

Hi @alexei-led I was wondering if there has been any update on this. Also, how can we use pumba to attack the process within the container? For example: Inject CPU/RAM...

Thanks @GeekyDeaks Just curious - I thought the configuration **duration: 30, arrivalRate: 1, and rampTo: 3** will ramp up to 3 users in 30 seconds. Or does the config mean...

@GeekyDeaks Yes, some confusion with rampTo as well. I had a question below regarding this. What does rampTo actually supposed to do when coupled with arrivalRate as shown below? ```...