Skip to content

Raspberry PI

Jump to bottom
Raymond Mouthaan edited this page Sep 25, 2019 · 7 revisions

[under construction]

This page describes specific information related to Raspberry PI and is intended for the Raspberry PI users, which uses Node-RED Docker images.

[BREAKING]

Native GPIO support

The replacement for native GPIO is node-red-node-pi-gpiod.

Disadvantages of the native GPIO support are:

  • Your Docker container needs to be deployed on the same Docker node/host on which you want to control the gpio's.
  • Gain access to /dev/mem of your Docker node/host
  • privileged=true is not supported for docker stack command

node-red-node-pi-gpiod solves all these disadvantages. With node-red-node-pi-gpiod it is possible to interact with gpio's of multiple Raspberry Pi's from a single Node-RED container.

Quick Migration steps to node-red-node-pi-gpiod

  1. Install node-red-node-pi-gpiod through the Node-RED pallete
  2. Install PiGPIOd daemon on the Raspberry PI where you want to interact wit it's gpio's.
  3. Configure node-red-node-pi-gpiod to connect to PiGPIOd daemon (ip-address or hostname based)
  4. For existing flows: replace all native gpio nodes with node-red-node-pi-gpiod

For install instruction details - please refer to the node-red-node-pi-gpiod README

arm32v6 vs arm32v7 vs arm64v8

With manifest list support Docker automatically detects on which architecture your Docker runs and pulls the corresponding image for it. This means for Raspberry PI 1 and Zero it pulls arm32v6 images and for Raspberry PI 2, 3 and 4 it pulls arm32v7 images. Although Raspberry PI 3 and later have 64 bit instruction sets, their operating systems like Raspbian are 32 bit compiled and therefor Docker detects arm32v7 instead of arm64v8.

Clone this wiki locally