Node-Red update in IOTstack

[bburkett52]

I am running Node-Red in IOTstack on RPi. Can anyone pout me in the right direction to update Node-Red to current?

Thanks
~Bob

[Paraphraser]

Hi,

First, please see this project is dormant. It explains why we (IOTstackers) had to fork Graham Garner's repo. You should seriously consider migrating (instructions are in the new repo).

Second, the magic incantation for forcing Node-Red to upgrade is:

$ cd ~/IOTstack
$ docker rmi nodered/node-red
$ docker-compose up --build -d nodered
$ docker system prune

In words, remove the base image. The --build flag forces the Dockerfile to be read to rebuild the local image if needed. The Dockerfile run discovers the missing base image and pulls it from Dockerhub, finds it's newer than the (missing) base used for the current local image, builds a new local image, and does a new-for-old swap at the last moment (so downtime for the Node-Red service is minimal). The prune gets rid of the old image.

And, third, it would be really helpful if you would close this issue. I keep trying to get people to do that so that the "this project is dormant" issue sits near the top where it is more likely to be noticed - with only limited success.🥺

[bburkett52]

Phil Thanks for your reply and direction! Wry much appreciated as I am a pretty casual user! Best regards ~Bob

On Mon, Nov 30, 2020 at 16:12 Phill ***@***.***> wrote: Hi, First, please see this project is dormant <#194>. It explains why we (IOTstackers) had to fork Graham Garner's repo. You should seriously consider migrating (instructions are in the new repo). Second, the magic incantation for forcing Node-Red to upgrade is: $ cd ~/IOTstack $ docker rmi nodered/node-red $ docker-compose up --build -d nodered $ docker system prune In words, remove the base image. The --build flag forces the Dockerfile to be read to rebuild the local image *if needed*. The Dockerfile run discovers the missing base image and pulls it from Dockerhub, finds it's newer than the (missing) base used for the current local image, builds a new local image, and does a new-for-old swap at the last moment (so downtime for the Node-Red service is minimal). The prune gets rid of the old image. And, third, it would be really helpful if you would close this issue. I keep trying to get people to do that so that the "this project is dormant" issue sits near the top where it is more likely to be noticed - with only limited success.🥺 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#219 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIOUEOE7Y5WS657MTCY62JDSSQDFFANCNFSM4UIBMHSA> .

-- [image: Weather Underground PWS KPASUMME3] <https://www.wunderground.com/dashboard/pws/KPASUMME3>

[bburkett52]

I'll be migrating to the new project!
Thanks for the help!
Regards,
Bob