missing node type after update from 1.1.3 to 1.2.x #206
Copy link
Copy link
Open
Description
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?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
Activity
dceejay commentedon Oct 16, 2020
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 lstype techniques then recover the contents and move them to a new (hopefully more permanent) volume.pinguinpfleger commentedon Oct 16, 2020
I have explicitly specified a volume to be mounted to /data.
dceejay commentedon Oct 17, 2020
Hmm odd - I would think that should work... did you try
-v nodered:/data? insteadpinguinpfleger commentedon Oct 21, 2020
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.