MQTTbench Docker

EQMX

• Source:

  • based on: 3.2 Alpine
  • final image: custom img

• Adaptation done:

  • add the following packages to the Dockerfile (via apk add):
    • iputils
    • iproute2
    • net-tools
    • iperf
    • busybox-extras
    • xterm (not working)
    • bash (not working)
  • change the user to root: USER root
  • install bash from the inside: apk add --no-cache bash

RABBITMQ

• Source:

  • based on: 3.8 Ubuntu
  • final image: custom img

• Adaptation done:

  • add the following packages to the Dockerfile (via apt-get):
    • net-tools
    • iputils-ping
    • iproute2

VerneMQ

• Source:

  • based on:
    • Debian
  • final image: custom img

• Adaptation done:

  • add the following packages to the Dockerfile (via apk add):
    • iputils
    • iproute2
    • net-tools
  • change the user to root: USER root

  In the Debian distribution, parameters can be passed through environmental parameters

  • Accept the license terms:
    • "DOCKER_VERNEMQ_ACCEPT_EULA": "yes" - env parameter
  • Allow anonymous communication:
    • "DOCKER_VERNEMQ_ALLOW_ANONYMOUS":"on"

  Alternitavely, these enviroment parameters can be preconfigured in the docker file

  • Accept the license terms:
    • ENV DOCKER_VERNEMQ_ACCEPT_EULA=yes
  • Allow anonymous communication:
    • DOCKER_VERNEMQ_ALLOW_ANONYMOUS=on

• Source:

  • based on:
    • 3.9 Alpine
  • final image: custom img

• Adaptation done:

  • add the following packages to the Dockerfile (via apk add):
    • iputils
    • iproute2
    • net-tools
    • iperf
    • xterm
    • busybox-extras
  • change the user to root: USER root

  In the Alpine distribution, parameters should be changed by means of command line commands

  • Accept the license terms:

    'echo "accept_eula = yes" >> /vernemq/etc/vernemq.conf'
    

  • Change the nodename of the MQTT docker

    `sed -i "/nodename = VerneMQ@127.0.0.1/s/= .*/= dev1@172.17.0.2/" /vernemq/etc/vernemq.conf`
    'sed -i "/VerneMQ@127.0.0.1/s/ .*/ dev2@172.17.0.3/" /vernemq/etc/vm.args'
    

HiveMQ

• Source:

  • based on: 4.2 HiveMQ
  • final image: custom img

• Adaptation done:

  • add the following packages to the Dockerfile (via apt-get):
    • net-tools
    • iputils-ping
    • iproute2

• DNS discovery image

  • The image has been configured with the discovery extension. This permits the creation of broker clusters.