I have a memory of Graham Garner saying something like "known issue - will need to be fixed sometime" when I struck this very same problem. There are quite a few things wrong with how NodeRed is built. Only a few days ago somebody pointed out that every command in the Dockerfile creates a new layer and that we would be better off creating a pseudo package (my words) where what the Dockerfile now installs became package dependencies. That strategy means a single new layer, apparently. In my own builds, I have adopted the approach of "install via the menu if it's in the menu, otherwise install via the Node-Red GUI" so I wind up with a mixture where some things follow the image (and need an image rebuild to update) while other just live in volumes and can be updated via the GUI plus a restart via the CLI. Because a full rebuild is so damn slow (particularly if SQLite is selected - which I need), I'm thinking it might be better to only offer through the menu those things that can ONLY be installed at image build time, leaving everything else for GUI installation. I don't quite get why SQLite needs to be compiled from scratch. Before IOTstack I was running NodeRed on macOS via "homebrew" and I just installed the SQLite support nodes via the GUI. Why doesn't that work on Raspbian+Docker? I need to find time to get to the bottom of all these mysteries... I also have half a mind to try raising a PR against the base image to see if they'll agree to add the eudev-dev dependency needed for Bluetooth support.

…

On 15 Jul 2020, at 18:14, Boris Hrubý ***@***.***> wrote: Thank you Paraphraser! You're the best! ;-) It indeed worked also for me. But I tried to stop just the nodered container. In the IOTstack menu there is an option to update all the containers, but it didn't work for me. At least for the Node-RED. Thanks again. Have a nice day! — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

Node-RED update to newest #89

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions