Contents
Cirrus Link Resources
Cirrus Link Website
Contact Us (Sales/Support)
Inductive Resources
Ignition User Manual
Knowledge Base Articles
Inductive University
Forum
Page History
...
- If Linux 64-bit is supported: cirruslink/ignition-edge-mqtt-linux-64:latest
- If Linux ARM HF is supported: cirruslink/ignition-edge-mqtt-linux-armhfarm32v7:latest
The repositories can be viewed here:
- https://hub.docker.com/r/cirruslink/ignition-edge-mqtt-linux-64/
- https://hub.docker.com/r/cirruslink/ignition-edge-mqtt-linux-armhf/arm32v7
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 'Use NFS volume" and 'Enable access control' is also are both disabled.
Repeat the volume creation process described above to create a second volume called 'ignition-bin'. When complete, the volumes should look as follows:
Step 4: Define and Start the Container
Now select 'Containers' on the left and click the 'Add Container' button. Set the following parameters:
- Name = IgnitionEdgeMQTTignition-edge-mqtt
- Image Name = (the image downloaded dependent on your hardware platform architecture)
- If Linux 64-bit is supported: cirruslink/ignition-edge-mqtt-linux-64:7.9.9latest
- If Linux ARM HF is supported: cirruslink/ignition-edge-mqtt-linux-armhf:7.9.9arm32v7:latest
- Always pull the image = not selected
- Publish all exposed ports = selected
- Map the following additional ports. Note you may need or want to change the first parameter (host port) depending on your platform
- 22 → 22 (TCP)
- 80 → 80 (TCP)
- 443 → 443 (TCP)
- 8000 → 8000 (TCP)
- 8043 → 8043 (TCP)
- 8060 → 8060 (TCP)
- 8088 → 8088 (TCP)
- Enable access control = not enabled
This is all shown below in the 64-bit Linux example.
In addition set the following advanced properties via the bottom tabs.
- Set the 'Command' to '/root/startup.sh' Map the Volumes as shown below.
- Map Set the Volumes Restart policy as shown below.
- Set the Restart policy to
- Leave all other 'Advanced container settings' default.
Finally, deploy 
Finally, start the container by clicking the 'Deploy the container' under the 'Actions' section as shown below.
After deploying you should see the new container now running as shown below.
Step 5: Connect to the
...
Ignition Edge Web UI and
...
start using Ignition Edge MQTT
...
At this point you are ready to configure and use Ignition Edge MQTT. The Ignition web UI is available on the docker port 8088. If you mapped 8088 → 8088, you can access the Ignition Web UI by browsing to
...
Download the latest MQTT Transmission from the Ignition download page here. Now browse to the new Ignition instance running as a Docker container. The URL will be http://localhost:8088 if you are running the Docker environment locally. Otherwise it would be accessible at http://[ipdocker_address_of_docker_environment]:8088. When logging in, use the default credentials of Ignition:
- Username: admin
- Password: password
Browse to the Configure tab on the top and then the Modules link on the left as shown below.
Now click the 'Install or Upgrade a Module...' link near the bottom of the main panel. Browse to the downloaded MQTT Transmission module and install it. When complete, it should look similar to what is shown below.
At this point you are ready to configure and use Ignition Edge MQTT. See the following two links for information on how to configure and use Ignition Edge MQTT.
Notes
If using a Hilscher Gateway with Docker support, make sure you set 'Docker Autostart' to 'enabled' as shown below.
Overview
Content Tools