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, Node-RED and npix-leds node to control LEDs of all LED supporting NPIX extension modules.
Base of this image builds debian with installed Internet of Things flow-based programming web-tool Node-RED and one extra node npix leds providing access to the LEDs of LED supporting NPIX modules over the GPIOs 22,23,25 and 26.
To allow the access to Node-RED over a web browser the container TCP port 1880 needs to be exposed to the host.
The node npix leds controls the NPIX LED signals across the GPIOs 22,23,25 and 26. Only an enabled privileged mode option lifts the enforced container limitations to allow usage of GPIOs in a container.
STEP 1. Open netPI's landing page under https://<netpi's ip address>.
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
-
Image:
hilschernetpi/netpi-nodered-npix-leds -
Port mapping:
Host "1880" (any unused one) -> Container "1880" -
Restart policy" :
always -
Runtime > Privileged mode :
On
STEP 4. Press the button Actions > Start/Deploy container
Pulling the image may take a while (5-10mins). Sometimes it takes so long that a time out is indicated. In this case repeat the Actions > Start/Deploy container action.
After starting the container open Node-RED in your browser with http://<netpi's ip address>:<mapped host port> e.g. http://192.168.0.1:1880. One extra node rfid leds in the nodes npix library palette provides you access to the LEDs of all LED supporting NPIX extension modules. The node's info tab in Node-RED explains how to use it.
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.
