hilscherautomation / netpi-mosquitto-mqtt-broker Goto Github PK

Made for netPI, the Raspberry Pi 3B Architecture based industrial suited Open Edge Connectivity Ecosystem

The image provided hereunder deploys a container with installed Debian and a Mosquitto MQTT server. This makes it suitable for handling the "Internet of Things" message protocol MQTT as a broker. MQTT clients on localhost or local area networks can use this broker for message distribution in the publish/subscribe model based manner.

Base of this image builds debian and the Mosquitto MQTT server in the version V1.4.14 supporting the MQTT protocol versions 3.1 and 3.1.1.

If the containerized MQTT server is used for message transactions of localhost MQTT clients hosted on netPI only then there is no need to map ports. Otherwise the ports 1883 and 8883 need to be mapped to free netPI host ports to get accessible over netPI's local area networks.

STEP 1. Open netPI's website in your browser (https).

STEP 2. Click the Docker tile to open the Portainer.io Docker management user interface.

STEP 3. Enter the following parameters under Containers > + Add Container

STEP 4. Press the button Actions > Start/Deploy container

Pulling the image may take a while (5-10mins). Sometimes it may take too long and a time out is indicated. In this case repeat STEP 4.

The container starts Mosquitto daemon automatically when started.

Start your clients, let them know netPI's IP address and publish/subscribe your topics and messages as usual across the broker.

The project complies with the scripting based Dockerfile method to build the image output file. Using this method is a precondition for an automated web based build process on DockerHub platform.

DockerHub web platform is x86 CPU based, but an ARM CPU coded output file is needed for Raspberry systems. This is why the Dockerfile includes the balena steps.

View the license information for the software in the project. As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained). As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

Hilscher Gesellschaft fuer Systemautomation mbH www.hilscher.com