July-20th-2021, 11:50 AM
(This post was last modified: July-21st-2021, 09:39 AM by Armin@netPI.)
Hello,
yes it is correct on HDMI log output any netPI device prints out "started update UTMP about System Runlevel Change" as last message. This is normal. Because netPI is a secured device there is no SSH service activated on netPI OS as you are use to with standard RPI3 or RPI4.
I also agree that using docker command cli to control docker engine as on standard RPI3 or RPI4 is sometimes easier than using portainer.io web tool to configure docker and containers. But if you got familiar with portainer.io after some deployments then it is much comfortable.
Q1: If you have configured hilscher node-red container well, then it ends up in the container state "healthy". This is a Docker feature you can enable for each container and makes a life check if the main application running in the container is still alive. And our hilscher node-red container supports this feature.
Q2: Yes it is correct that the hilscher node-red container needs to be configured in mode "host". But you are not bound to use the hilscher node-red container in any case. You can also deploy a common and standard node-red container from here https://hub.docker.com/r/nodered/node-red/. This container does not necessarily be configured in mode "host" and can run in mode "bridged" also. It is your choice which one you want to use and of course it depends on what you want to realize as your final application. But since hilscher node-red container is sepcial and supports things like bluetooth also or the onboard industrial network controller chip for real-time ethernet communications ... all those features need direct hardware access and this is why hilscher node-red container needs to run in "host" mode.
Q3: In order to install MQTT broker on netPI I recommend this one here https://hub.docker.com/_/eclipse-mosquitto. Since you are describing you want to access from netPI node-red container (which is running in host mode) to local MQTT broker which can run in "bridge" mode use the containers IP address as destination in your node-red MQTT in/out node.
For more details about how to get it running read on this thread https://forum.hilscher.com/thread-269.html. Mosquitto container by default is unconfigured and need edits in mosquitto.conf file as explained in the thread. If you do not modify the *.conf file Mosquitto MQTT broker will not work
Q4: see thread https://forum.hilscher.com/thread-269.html. I have tested it just a minute ago and got my MQTT node connect to my local mqtt container
mqtt_broker.jpg (Size: 4.74 KB / Downloads: 18)
Thx
Armin
yes it is correct on HDMI log output any netPI device prints out "started update UTMP about System Runlevel Change" as last message. This is normal. Because netPI is a secured device there is no SSH service activated on netPI OS as you are use to with standard RPI3 or RPI4.
I also agree that using docker command cli to control docker engine as on standard RPI3 or RPI4 is sometimes easier than using portainer.io web tool to configure docker and containers. But if you got familiar with portainer.io after some deployments then it is much comfortable.
Q1: If you have configured hilscher node-red container well, then it ends up in the container state "healthy". This is a Docker feature you can enable for each container and makes a life check if the main application running in the container is still alive. And our hilscher node-red container supports this feature.
Q2: Yes it is correct that the hilscher node-red container needs to be configured in mode "host". But you are not bound to use the hilscher node-red container in any case. You can also deploy a common and standard node-red container from here https://hub.docker.com/r/nodered/node-red/. This container does not necessarily be configured in mode "host" and can run in mode "bridged" also. It is your choice which one you want to use and of course it depends on what you want to realize as your final application. But since hilscher node-red container is sepcial and supports things like bluetooth also or the onboard industrial network controller chip for real-time ethernet communications ... all those features need direct hardware access and this is why hilscher node-red container needs to run in "host" mode.
Q3: In order to install MQTT broker on netPI I recommend this one here https://hub.docker.com/_/eclipse-mosquitto. Since you are describing you want to access from netPI node-red container (which is running in host mode) to local MQTT broker which can run in "bridge" mode use the containers IP address as destination in your node-red MQTT in/out node.
For more details about how to get it running read on this thread https://forum.hilscher.com/thread-269.html. Mosquitto container by default is unconfigured and need edits in mosquitto.conf file as explained in the thread. If you do not modify the *.conf file Mosquitto MQTT broker will not work
Q4: see thread https://forum.hilscher.com/thread-269.html. I have tested it just a minute ago and got my MQTT node connect to my local mqtt container
mqtt_broker.jpg (Size: 4.74 KB / Downloads: 18)
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
