# Node-RED integration to launch a container with one click **URL:** \ **Category:** Demandes livrées\ **Tags:** feature-integration, node-red\ **Created:** [October 10, 2021, 7:52pm UTC](https://community.gladysassistant.com/t/integration-node-red-pour-lancer-un-container-en-un-clic/6584 "2021-10-10T19:52:29Z")\ **Posts on this page:** 20\ **Page:** 7
**Author:** ![cce66](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/8797f3/32.png) [@cce66](https://community.gladysassistant.com/u/cce66)\ **Post date:** [September 26, 2023, 10:52pm UTC](https://community.gladysassistant.com/t/integration-node-red-pour-lancer-un-container-en-un-clic/6584/121 "2023-09-26T22:52:51Z")
Hi @Psoy@Lokkye > [@Psoy](#): > > ```auto > -v /var/lib/gladysassistant_test_nodered:/var/lib/gladysassistant \ > > ``` > > by > > ```auto > -v /var/lib/gladysassistant:/var/lib/gladysassistant \\ > > ``` > > that works, Indeed, after purging the containers and restarting with docker run -d --log-opt max-size=10m --restart=always --privileged --network=host --name gladys-test-nodered -e NODE\_ENV=production -e SERVER\_PORT=8010 -e TZ=Europe/Paris -e SQLITE\_FILE\_PATH=/var/lib/gladysassistant/gladys-production.db -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/gladysassistant:/var/lib/gladysassistant -v /dev:/dev -v /run/udev:/run/udev:ro delogzway/gladys:nodered everything works perfectly 🤪 Bravo @Lokkye 👏 A thousand thanks — this will make Gladys much more attractive because it’s now open to everything in a simple way via Node-RED! A real breakthrough! 👍 Quick question: Will it be possible to change the credentials afterwards or even choose to enable or disable authentication, or to launch via ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/2X/7/7c8d3c21b6eae65e2571cc43c33d835f67d7fe38.png) without having to authenticate again afterwards? Same for the port? ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [September 27, 2023, 6:56am UTC](https://community.gladysassistant.com/t/integration-node-red-pour-lancer-un-container-en-un-clic/6584/122 "2023-09-27T06:56:52Z")
@Psoy @cce66 This is not a solution, it really needs to work even without the `/var/lib/gladysassistant` volume, otherwise it will crash for all users who are on Synology/Unraid, and any other platform where the volume is different! @Lokkye Any idea what might be wrong? Can you reproduce it? ---
**Author:** ![Lokkye](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/lokkye/32/5881_2.png) [@Lokkye](https://community.gladysassistant.com/u/Lokkye)\ **Post date:** [September 27, 2023, 6:57am UTC](https://community.gladysassistant.com/t/integration-node-red-pour-lancer-un-container-en-un-clic/6584/123 "2023-09-27T06:57:30Z")
I am running tests on my side. I noticed some minor issues. I am fixing them. ---
**Author:** ![cce66](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/8797f3/32.png) [@cce66](https://community.gladysassistant.com/u/cce66)\ **Post date:** [September 27, 2023, 7:39am UTC](https://community.gladysassistant.com/t/integration-node-red-pour-lancer-un-container-en-un-clic/6584/124 "2023-09-27T07:39:29Z")
Hello @pierre-gilles @Lokkye True, but is it really useful to have 2 separate Node-RED instances and why should @Lokkie’s instance have a different path? It seems more coherent to me that the path be that of gladysassistant now that Node- ---
**Author:** ![Lokkye](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/lokkye/32/5881_2.png) [@Lokkye](https://community.gladysassistant.com/u/Lokkye)\ **Post date:** [September 27, 2023, 8:09am UTC](https://community.gladysassistant.com/t/integration-node-red-pour-lancer-un-container-en-un-clic/6584/125 "2023-09-27T08:09:56Z")
@pierre-gilles @cce66 @Psoy I just understood the problem — an issue with « basePathOnContainer » and « basePathOnHost ». I just released a new version of the Docker image. I’ve tested it in every way (first startup, restart, deleting the node-red folder, changing the volume, …) Don’t hesitate to pull and give me feedback (thanks in advance) > [@cce66](#): > > Granted, but is it really useful to have 2 distinct Node-RED instances and why should @Lokkie’s instance have a different path? I don’t have a different path. I just need to install the Node-RED configs in the Gladys folder to be compatible with all possible installations. > [@cce66](#): > > It seems more coherent to me that the path be that of GladysAssistant now that Node-RED is integrated and managed by Gladys, especially since that would allow saving the flows, right? That’s exactly it > [@cce66](#): > > What needs to be done, I think, is to ensure that the transition from the old method of managing Node-RED to the new Node-RED management handled by Gladys is transparent and without data loss. I don’t know if that can be automatic because until now the Node-RED instances were not known to Gladys. However I just saw that there is the possibility to do exports and imports in Node-RED. So I would recommend doing the exports/imports manually from the old instance to the new Node-RED instance. ---
**Author:** ![cce66](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/8797f3/32.png) [@cce66](https://community.gladysassistant.com/u/cce66)\ **Post date:** [September 27, 2023, 10:27am UTC](https://community.gladysassistant.com/t/integration-node-red-pour-lancer-un-container-en-un-clic/6584/126 "2023-09-27T10:27:26Z")
@Lokkye I don’t remember where it changed but to access Gladys from your test image what were the credentials again (I can’t access [http://192.168.0.xxx:8010](http://192.168.0.xxx:8010) but I can access Node-RED [http://192.168.0.xxx:1881](http://192.168.0.xxx:1881)) > [@Lokkye](#): > > I don’t know if that can be automatic because until now the Node-RED instances were not known to Gladys. However I just saw that it’s possible to do exports and imports in Node-RED. So I would recommend doing the exports/imports manually from the old instance to the new Node-RED instance. yes but that doesn’t import, among other things, the node\_modules necessary for the flows by copying /var/lib/node-red/node\_modules/ to /var/lib/gladysassistant/node-red/node\_modules/ that loads them but there remain credential problems as well ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/2X/d/d70654701d56e3490f45234f438add5f599ca0d6.png) maybe take inspiration from [Tutorial] Automatic Backup of Node-RED [https://www.youtube.com/watch?v=l56VQgTpVBY](https://www.youtube.com/watch?v=l56VQgTpVBY) by modifying it to make a backup of the old Node-RED and a restore to the new one? I’ll try to see… Apparently it’s enough to copy the contents of /var/lib/node-red to /var/lib/gladysassistant/node-red I confirm that by making the copy we recover everything and it works perfectly! @lokkie @pierre-gilles however a homekit and mosquitto directory is created in the test dir, normal? ---
**Author:** ![cce66](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/8797f3/32.png) [@cce66](https://community.gladysassistant.com/u/cce66)\ **Post date:** [September 27, 2023, 12:14pm UTC](https://community.gladysassistant.com/t/integration-node-red-pour-lancer-un-container-en-un-clic/6584/127 "2023-09-27T12:14:26Z")
@lokkie after stopping and removing the containers after docker pull the new image with docker pull delogzway/gladys:nodered and started the container with docker run -d --log-opt max-size=10m --restart=always --privileged --network=host --name gladys-test-nodered -e NODE\_ENV=production -e SERVER\_PORT=8010 -e TZ=Europe/Paris -e SQLITE\_FILE\_PATH=/var/lib/gladysassistant/gladys-production.db -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/gladysassistant\_test\_nodered:/var/lib/gladysassistant -v /dev:/dev -v /run/udev:/run/udev:ro delogzway/gladys:nodered ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/2X/0/00207f20b814c2558044914b6c20dd5dbe3d99cc.jpeg) I enable Node-RED ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/2X/3/348b3c27f2ab532632b60ea21df149dfa807c2b6.png) I disable it and I get ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/2X/7/785e41e050a48534ebb42569862a62bef458ecc8.png) I have to do a refresh to get ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/2X/8/8c90e1447470891e20f9fa6eb0442f52a13bc37e.png) and be able to activate it again By the way, on the first login (after installation), I enter the credentials and I cannot log in to Node-RED (invalid credentials), I disable Node-RED, I re-enable it and then I can log in — afterwards no problem, it connects normally without requesting authentication, maybe autofill of the fields? I restart the node\_red container, and I can access my old Node-RED with its flows on port 1880 apparently only the JSON files at the root need to be copied flows.json contains the flows and package.json contains the names of the modules required for the flows this may help https://www.youtube.com/embed/Os2wrgeqQMg?feature=oembed&wmode=opaque https://www.youtube.com/embed/az0QMwdBcYk?feature=oembed&wmode=opaque it should be possible, when you activate the Node-RED container, to get the path of the 1st Node-RED container and that of the 2nd Node-RED container (version @lokkie) and copy the contents of the 1st into the 2nd before launching Node-RED (version @lokkie), if you want? ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [September 27, 2023, 5:05pm UTC](https://community.gladysassistant.com/t/integration-node-red-pour-lancer-un-container-en-un-clic/6584/128 "2023-09-27T17:05:43Z")
> [@Lokkye](#): > > I don’t know if that can be automatic because until now the Node-RED instances were not known to Gladys. I don’t think that can be automatic either, the Gladys instance doesn’t have access to the folders currently used. Anyway, this integration is only intended for an audience that doesn’t know how to run Node-RED themselves. If you’ve already run Node-RED yourself, there’s little reason for you at the moment to run it inside Gladys… ^^ > [@cce66](#): > > @pierre-gilles by the way there is a creation of the homekit and mosquitto directory in the test repo, normal? Yes. ---
**Author:** ![cce66](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/8797f3/32.png) [@cce66](https://community.gladysassistant.com/u/cce66)\ **Post date:** [September 27, 2023, 7:45pm UTC](https://community.gladysassistant.com/t/integration-node-red-pour-lancer-un-container-en-un-clic/6584/129 "2023-09-27T19:45:41Z")
@pierre-gilles@Lokkye > [@pierre-gilles](#): > > I don’t think it can be automatic either; the Gladys instance doesn’t have access to the folders currently used. That’s true, when this integration is formalized it will be enough to provide the necessary info or even include it in the integration’s documentation > [@cce66](#): > > Apparently you just need to copy the contents of > /var/lib/node-red > to > /var/lib/gladysassistant/node-red > [@pierre-gilles](#): > > Anyway, this integration is only aimed at an audience that doesn’t know how to run Node-RED themselves. If you’ve already run Node-RED yourself, there’s little point for you right now in running it inside Gladys… ^^ Ah well I’m not agreeing there because for « Gladys Plus » users it’s a plus to be able to back up their Node-RED environment — well, if the /var/lib/gladysassistant/node-red directory is included in the backup (in that case you should back up only the essential items as specified in the video because I assume you have a limit on backup size) @pierre-gilles afterwards you could make a video for anglophobes showing how to back up the existing Node-RED to restore it into the one managed by Gladys, I’m just saying! 😉 ---
**Author:** ![Psoy](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/psoy/32/9005_2.png) [@Psoy](https://community.gladysassistant.com/u/Psoy)\ **Post date:** [September 27, 2023, 8:32pm UTC](https://community.gladysassistant.com/t/integration-node-red-pour-lancer-un-container-en-un-clic/6584/130 "2023-09-27T20:32:25Z")
> [@Lokkye](#): > > Don’t hesitate to pull and give me feedback (thanks in advance) Good evening @Lokkye Here I just retested, so now it works with the command ```auto -v /var/lib/gladysassistant_test_nodered:/var/lib/gladysassistant \ ``` Like @cce66, after clicking on the NodeRed link, I can access the NodeRed page, however the copy/paste of the credentials does not work on the first try (connection failure). I had to deactivate NodeRed, then reactivate it, and then the copy/paste worked and I can access NodeRed. ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [September 28, 2023, 7:31am UTC](https://community.gladysassistant.com/t/integration-node-red-pour-lancer-un-container-en-un-clic/6584/131 "2023-09-28T07:31:24Z")
[quote=« cce66, post:129, topic:6584 »] Ah well, I don’t agree because for « Gladys Plus » users ---
**Author:** ![cce66](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/8797f3/32.png) [@cce66](https://community.gladysassistant.com/u/cce66)\ **Post date:** [September 28, 2023, 7:48am UTC](https://community.gladysassistant.com/t/integration-node-red-pour-lancer-un-container-en-un-clic/6584/132 "2023-09-28T07:48:34Z")
Hello @pierre-gilles, Gadzooks, drat, blast, balderdash and thunderation! 💣 I’m disappointed 😭 Too bad because in terms of backup it doesn’t represent much data, well maybe in the future… 🙂 > [@pierre-gilles](#): > > Anyway, this integration is only aimed at an audience that doesn’t know how to run Node-RED themselves. If you’ve already run Node-RED yourself, you have little interest for now in running it inside Gladys… ^^ Well, let’s say that since we couldn’t do otherwise before… now when this integration is operational, I’ll do a clean install again keeping only the management through Gladys ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [September 28, 2023, 7:52am UTC](https://community.gladysassistant.com/t/integration-node-red-pour-lancer-un-container-en-un-clic/6584/133 "2023-09-28T07:52:09Z")
@Lokkye So can you add a message in the interface saying that Node-RED is not backed up by Gladys Plus, and that if the user wants to back up their Node-RED instance they need to manually export their flows in Node-RED or set up automatic backups on the Node-RED side? It will be clearer and avoid confusion. ---
**Author:** ![spenceur](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/spenceur/32/1961_2.png) [@spenceur](https://community.gladysassistant.com/u/spenceur)\ **Post date:** [September 28, 2023, 8:06am UTC](https://community.gladysassistant.com/t/integration-node-red-pour-lancer-un-container-en-un-clic/6584/134 "2023-09-28T08:06:46Z")
> [@pierre-gilles](#): > > Gladys Plus will not back up Node-RED, that’s not part of this development. Hello, However, if we create a request specifically for that, do we agree it could be done? Personally I wouldn’t use this integration, but it was just to understand your remark « that’s not part of this development » 🙂 ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [September 28, 2023, 8:19am UTC](https://community.gladysassistant.com/t/integration-node-red-pour-lancer-un-container-en-un-clic/6584/135 "2023-09-28T08:19:51Z")
> [@spenceur](#): > > However, if one creates a request specifically for that, we agree that it can be done? No idea; from what I’ve seen so far I don’t think so, but I’m not a Node-RED expert 🙂 ---
**Author:** ![Lokkye](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/lokkye/32/5881_2.png) [@Lokkye](https://community.gladysassistant.com/u/Lokkye)\ **Post date:** [September 28, 2023, 8:52am UTC](https://community.gladysassistant.com/t/integration-node-red-pour-lancer-un-container-en-un-clic/6584/136 "2023-09-28T08:52:57Z")
I’ve just released a new image with : - The fix for the connection on first launch - The button display when Node-RED is disabled A vos tests, prêt, partez 🙂 @pierre-gilles, For the backup, if I find a way to export and import the Node-RED information, do you think that could be sent to the Gladys Plus backup? (in terms of volume/price of the subscription) ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [September 28, 2023, 8:57am UTC](https://community.gladysassistant.com/t/integration-node-red-pour-lancer-un-container-en-un-clic/6584/137 "2023-09-28T08:57:18Z")
> [@Lokkye](#): > > For the backup, if I find a way to export and import the Node-RED information, do you think that could be sent to the Gladys Plus backup? (in terms of volume/price of the subscription) What we do on the Zigbee2mqtt side is that Zigbee2mqtt provides an API that exports in JSON format all the parameters that allow restoring an instance from scratch, and we store that JSON in a « variable » in the DB 🙂 Thus, the backup is included in Gladys Plus, and the Zigbee2mqtt integration checks for the presence of the variable when Gladys starts, and restores Zigbee2mqtt. If Node-RED provides an API, why not. However, you mustn’t naively back up the filesystem; that’s the best way to end up with a corrupted backup (and above all, we’re not going to bother backing up node\_modules in Gladys Plus). If Node-RED doesn’t provide an API, then it’s not possible… ---
**Author:** ![cce66](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/8797f3/32.png) [@cce66](https://community.gladysassistant.com/u/cce66)\ **Post date:** [September 28, 2023, 8:57am UTC](https://community.gladysassistant.com/t/integration-node-red-pour-lancer-un-container-en-un-clic/6584/138 "2023-09-28T08:57:41Z")
Apparently you just need to add a variable that defines the external path to which the flows will be saved ```auto -v /var/lib/gladysassistant_test_nodered/node-red/data:/data ``` > **[Running under Docker : Node-RED](https://nodered.org/docs/getting-started/docker)** > ### Managing User Data > > Once you have Node-RED running with Docker, we need to ensure any added nodes or flows are not lost if the container is destroyed. This user data can be persisted by mounting a data directory to a volume outside the container. This can either be done using a bind mount or a named data volume. > > Node-RED uses the `/data` directory inside the container to store user configuration data. > > #### Using a Host Directory for Persistence (Bind Mount) > > To save your Node-RED user directory inside the container to a host directory outside the container, you can use the command below. To allow access to this host directory, the node-red user (default uid=1000) inside the container must have the same uid as the owner of the host directory. > > ```auto > docker run -it -p 1880:1880 -v /home/pi/.node-red:/data --name mynodered nodered/node-red > > ``` > > In this example the host `/home/pi/.node-red` directory is bound to the container `/data` directory. > > **Note** : Users migrating from version 0.20 to 1.0 will need to ensure that any existing `/data` directory has the correct ownership. As of 1.0 this needs to be `1000:1000`. This can be forced by the command `sudo chown -R 1000:1000 path/to/your/node-red/data` > > See [the wiki](https://github.com/node-red/node-red-docker/wiki/Permissions-and-Persistence) for detailed information on permissions. I’ll run tests this afternoon for that, in case it’s just a line to add… 😉 Ah well no I can’t, it’s a line to modify in the command that @lokkie runs in his integration snif 😪 🥲 it’s @lokkie the master of the keys 😭 🤣 ---
**Author:** ![cce66](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/8797f3/32.png) [@cce66](https://community.gladysassistant.com/u/cce66)\ **Post date:** [September 28, 2023, 8:59am UTC](https://community.gladysassistant.com/t/integration-node-red-pour-lancer-un-container-en-un-clic/6584/139 "2023-09-28T08:59:17Z")
@pierre-gilles > [@pierre-gilles](#): > > If Node-RED offers an API, why not. After that, you mustn’t naively back up the filesystem; that’s the best way to end up with a corrupted backup (and above all, we’re not going to bother backing up node\_modules in Gladys Plus). If Node-RED doesn’t offer an API, then it’s not possible… No, there’s no need — the file /var/lib/gladysassistant\_test\_nodered/node-red/packages.json includes the list of modules required by the flows and if they are missing they are reinstalled yes there are APIs but after that I don’t know how this can be implemented by @lokkie > **[Storage API : Node-RED](https://nodered.org/docs/api/storage/)** > Storage API > > The Storage API provides a pluggable way to configure where the Node-RED runtime stores data. > > The information stored by the API includes: > > ``` > flow configuration > flow credentials > user settings > user sessions > node library content > > ``` and the methods for this API here > **[Storage API : Node-RED](https://nodered.org/docs/api/storage/methods/)** ---
**Author:** ![cce66](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/8797f3/32.png) [@cce66](https://community.gladysassistant.com/u/cce66)\ **Post date:** [September 28, 2023, 9:26am UTC](https://community.gladysassistant.com/t/integration-node-red-pour-lancer-un-container-en-un-clic/6584/140 "2023-09-28T09:26:12Z")
There’s an interesting passage here > **[Node-Red et Home Assistant sur Docker](https://technologie-geek.fr/node-red-et-home-assistant-sur-docker/)** > > Installation de Node-Red sur Docker avec Home Assistant. Node-Red vous permet de développer visuellement vos flux de données. > When installing Node-Red on Docker, your volume for the data directory was created by and belongs to our user **« root »** , whose identifier is **« uid=0 gid=0 »**. The Node-Red user inside the container, which owns the /data directory, however has different identifiers: **« uid=1000 gid=1000 »**. You can resolve this issue by connecting via SSH to your server and changing the ownership of the Docker volume to the user with ID 1000:1000 by running the following command: > > I’m connected as **« root »** , the **« sudo »** command is not necessary, but I’m including it just in case. > > ```auto > sudo chown -R 1000:1000 /mnt/node-red/data > > ``` So you’ll need to set the same ownership, I think, on ```auto var/lib/gladysassistant_test_nodered/node-red/data ``` After that, it’s true that this applies to a Linux setup; on Windows (I don’t think there will be any problems) and on Synology I don’t know (although Syno is Linux-based at its core, but maybe Synology has a built-in backup option if Synology users can provide an answer) [Previous page](https://community.gladysassistant.com/t/integration-node-red-pour-lancer-un-container-en-un-clic/6584.md?page=6) [Next page](https://community.gladysassistant.com/t/integration-node-red-pour-lancer-un-container-en-un-clic/6584.md?page=8)