Demonstrating Docker-Ready Solution for Apache Jmeter

Tested Infrastructure

Platform Number of Instance Reading Time
Play with Docker 5 5 min


cloning ng the Repository

$git clone
$cd jmeter-docker

Running Docker Compose</b>

$docker-compose up -d

It will push jmeter-master to the master node and jmeter-server to the slave nodes and make it ready to start load using the external JMX file.

$ docker service ls
              ID            NAME         MODE        REPLICAS  IMAGE
              mlffd5djek3t  myjm_slave   replicated  3/3       ajeetraina/jmeter-server:latest
              rv1r3cjvzkg3  myjm_master  replicated  1/1       ajeetraina/jmeter-master:latest

Let us verify these containers on both the nodes:

@master:~$ docker ps
          CONTAINER ID        IMAGE                                                                                                     
          COMMAND             CREATED             STATUS              PORTS               NAMES
          4954e3ef40f6        ajeetraina/jmeter-master@sha256:1ad38973587725480e76a8914463c674ca95ddfe32e180e4695b8f9150c34981       
          "/bin/bash"         2 hours ago         Up 2 hours          60000/tcp           myjm_master.1.bz2r7rrdrzomqwv56dpxi0m08

Use the same command to verify on the slave nodes.

Pushing the JMX file into the container</b>

$docker exec -i <container-running-on-master-node> sh -c 'cat > /jmeter/apache-jmeter-2.13/bin/jmeter-docker.jmx' < jmeter-docker.jmx

Starting the Load testing

$docker exec -it <container-on-master-node> bash
      root@4954e3ef40f6:/#cd /jmeter/apache-jmeter-2.13/bin
      $./jmeter -n -t jmeter-docker.jmx -R<list of containers running on slave nodes seperated by commas)

Handful Commands

Listing the Slave IPs

$ docker inspect --format ' => ' $(sudo docker ps -a -q)

Stopping all the containers in a single shot

$docker stop $(docker ps -a -q)


Ajeet S Raina