nodered: mount its settings where the image's health check reads them #186

2026-09-30T16:28:07Z

mesh-admin commented

2026-09-30 16:28:07 +00:00

The image's /healthcheck.js does require("/data/settings.js"); the mesh mounted the rendered settings at /config/settings.js, so nodered ran fine (editor 200) but docker reported it unhealthy forever (seen on ace after W11). The manifest vocabulary has no health-check override, so the same file is now mounted at /data/settings.js and --settings points there.

The image's `/healthcheck.js` does `require("/data/settings.js")`; the mesh mounted the rendered settings at `/config/settings.js`, so nodered ran fine (editor 200) but docker reported it unhealthy forever (seen on ace after W11). The manifest vocabulary has no health-check override, so the same file is now mounted at `/data/settings.js` and `--settings` points there.

mesh-admin added 1 commit 2026-09-30 16:28:07 +00:00

nodered: mount its settings where the image's health check reads them 82686e44f3

The image's /healthcheck.js requires /data/settings.js, so with the mesh's
settings mounted at /config the container ran fine but reported unhealthy
forever. Mount the same file at /data/settings.js and point --settings there.

mesh-admin merged commit c91d12a11d into main

2026-09-30 16:28:09 +00:00

mesh-admin deleted branch fix/nodered-healthcheck-settings-path

2026-09-30 16:28:09 +00:00

mesh-admin referenced this pull request

2026-09-30 16:32:13 +00:00

nodered: settings.json sits beside settings.js #187

jschoubben referenced this issue from a commit

2026-09-30 16:32:13 +00:00

nodered: settings.json sits beside settings.js, which reads it from its own directory

Sign in to join this conversation.