July-20th-2021, 11:10 AM
(July-14th-2021, 11:41 AM)Armin@netPI Wrote: Hi Armin, thanks, also goes to Ms. Xia.
I went through the youtube clips, it's very helpful. I am working on NIOT-E-NPI3-EN-RE. My first container Raspbian works, and I could sudo update it well.
I checked the status of NPI3 from its HDMI, it pends at "started update UTMP about System Runlevel Change". I assume that's expected as design. and users should access the device through main-control-center.
When you say you could access all netpi from anywhere of your office, must all those netpis wire connected?
It was not easy to get Nodered container downloaded and run. Part of the difficulty was contributed from the public network to dockerhub, partly from the proxy of the remote desktop I am using. Part may contribute from the cache of the browser. In general, I could "docker pull hilscher-netpi/netpi-nodered" much faster from a PI4, than netpi3.
Q1: confusion on nodered status "healthy", not "running"?
Q2: when starting a container, the network attribute could be "host", "bridge".... typically we use "host". can you elaborate on it? If we have a MQTT container runs along side with NodeRed container. If NodeRed takes "host", how to configure MQTT into container network, so that the broker (server) is "visible" by the nodered nodes?
Q3: Given an Netpi, how can I have MQTT installed natively as Portainer?
Thanks.
Yongzhi
