missing node type after update from 1.1.3 to 1.2.x

[pinguinpfleger]

nodered stoppen working after watchtower upgraded nodered to 1.2.0 due to missing node types.

Example:

Flows stopped due to missing node types.

hue-bridge
light-scheduler-settings
influxdb
harmonyws-server
hb-conf
nuki-bridge
zigbee2mqtt-server
hue-group
hue-bridge-node
cron
hue-light
influxdb in
influxdb out
harmonyws-observer
nuki-bridge-control
nuki-lock-control
harmonyws-command
stoptimer
hue-magic
light-scheduler-filter
shelly-switch
harmonyws-activity
door-sensor
zigbee2mqtt-bridge
zigbee2mqtt-get
zigbee2mqtt-out

Why did it happen? How can it get fix? How can it be prevented in the future?

[dceejay]

this may be because we have removed the volume statement from the default build

see here - for details - https://github.com/node-red/node-red-docker/blob/master/volumechanges.md

If that is the case then the old volume will still be there - but not linked - you will need to find it using standard docker volume ls type techniques then recover the contents and move them to a new (hopefully more permanent) volume.

[pinguinpfleger]

I have explicitly specified a volume to be mounted to /data.

docker volume create nodered

docker run -d --restart=unless-stopped \
  --name nodered \
  -e TZ="Europe/Berlin" \
  --mount source=nodered,target=/data \
  --user="1000:1000" \
  -p 1880:1880 \
  nodered/node-red

 l /var/lib/docker/volumes/nodered/_data/
insgesamt 668K
-rw-r--r--   1 pi   pi    16K Okt 15 23:41 .config.json
-rw-r--r--   1 pi   pi    32K Okt 15 23:41 .config.json.backup
-rw-r--r--   1 pi   pi    23K Okt 16 00:16 .config.nodes.json
-rw-r--r--   1 pi   pi    23K Okt 16 00:16 .config.nodes.json.backup
-rw-r--r--   1 pi   pi      2 Okt 16 00:16 .config.projects.json
-rw-r--r--   1 pi   pi      2 Okt 16 00:16 .config.projects.json.backup
-rw-r--r--   1 pi   pi     95 Okt 16 00:16 .config.runtime.json
-rw-r--r--   1 pi   pi     95 Okt 16 00:16 .config.runtime.json.backup
-rw-r--r--   1 pi   pi    461 Okt 16 00:16 .config.users.json
-rw-r--r--   1 pi   pi    460 Okt 16 00:16 .config.users.json.backup
-rw-r--r--   1 pi   pi    640 Aug 30 21:36 flows_cred.json
-rw-r--r--   1 pi   pi    640 Aug 30 20:37 .flows_cred.json.backup
-rw-r--r--   1 root root  204 Aug 30 21:36 flows_homebridge_cred.json
-rw-r--r--   1 root root  57K Aug 30 21:36 flows_homebridge.json
-rw-r--r--   1 pi   pi   147K Okt  3 20:58 flows.json
-rw-r--r--   1 pi   pi   147K Okt  3 19:02 .flows.json.backup
drwxr-xr-x   3 pi   pi   4,0K Aug 30 20:32 lib
drwxr-xr-x 364 pi   pi    12K Okt 15 22:55 node_modules
drwxr-xr-x   5 pi   pi   4,0K Okt 15 22:55 .npm
-rw-r--r--   1 pi   pi    296 Okt 15 22:55 package.json
-rw-r--r--   1 pi   pi   138K Okt 15 22:55 package-lock.json
-rw-r--r--   1 pi   pi    14K Aug 30 20:32 settings.js

[dceejay]

Hmm odd - I would think that should work... did you try -v nodered:/data ? instead

[pinguinpfleger]

In the meantime II added all missing add ons via the web interface. Not the most elegant variant but at least it works. Somehow it is still from interest what happened and what can be done to prevent outages like that.