Installing Ignition Edge MQTT as a Docker Container

Prerequisites

• Ensure you have a platform that supports either Linux 64-bit Docker images or ARM HF images
• Hilscher provides a number of gateways that support 64-bit Linux containers and ARM HF containers
  • https://www.hilscher.com/products/product-groups/industrial-internet-industry-40/netiot-edge/
  • https://www.netiot.com/netpi/industrial-raspberry-pi-3/
• This tutorial will use Portainer to set up and configure the container.  However, this could all be done via the command line if you prefer.

Summary

This tutorial will cover the downloading, configuration, and starting of Ignition Edge MQTT as a Docker container using Portainer.

Upon completion of this tutorial you will have Ignition Edge MQTT installed as a Docker container which will be ready to configure and use.

Tutorial

Step 1: Start Portainer

Begin by ensure Portainer is running and you are set up to manager the target Docker environment.  Information on Portainer can be found here.  If using a Hilscher Edge device consult the Hilscher documentation for access to the Portainer Portal.

Step 2: Download the Ignition Edge MQTT image

Open a Web Browser to your Portainer instance and select images on the left.  In the name section enter one of the two following strings depending on your platform architecture:

• If Linux 64-bit is supported: cirruslink/ignition-edge-linux-64:7.9.9
• If Linux ARM HF is supported: cirruslink/ignition-edge-linux-armhf:7.9.9

Shown below is an example for 64-bit Linux.  After entering the target image into the name field, click the 'Pull the Image' button to download it.  You must have internet connectivity for this to succeed.

Once the download is complete, you should see something similar to the following.

Step 3: Create the Volumes

Select volumes on the left and add two new ones by clicking the 'Add Volume' button.  Then type the name of the first volume as 'ignition-data' as shown below and click 'Create the volume'.  Ensure 'Access control' is also disabled.

Repeat the volume creation process described above to create a second volume called 'ignition-bin'.

Step 4: Define and Start the Container