\nHello @tiboys \nI’m planning, for next time, to block Node-RED updates by Watchtower, as recommended by @spenceur
Mmm we’ll see because it’s not only the Gladys container to monitor but also Zigbee2mqtt and mosquitto, containers that aren’t installed by default. We want updates for these last two as well, because new devices are very regularly added to Z2M. In a few months I hope we’ll release the ZwaveJS2Mqtt integration; there will also be a container to update. You have to think long term, because these images can easily be used for 4-5 years 
Also, generally speaking, it’s good practice to keep these pieces of software up to date; you just have to respect SemVer (SemVer — Wiktionnaire, le dictionnaire libre) to only follow the minor versions of a fixed major version.
I rather think we should maybe take the problem the other way around — the only « issue » here is that the command I highlighted to launch Node-RED was « latest », whereas I could have highlighted the tagged major version, which would have avoided any problem here.
In the same way that the command to launch Gladys that I provide on the site is locked to the major version « v4 », the day we move to v5 with breaking changes, users on v4 will not be impacted:
hello @spenceur
the command you gave me doesn’t work as-is, I get this output:
"docker run" requires at least 1 argument.
See 'docker run --help'.
Usage: docker run [OPTIONS] IMAGE [COMMAND] [ARG...]
Run a command in a new container
-bash: -v: command not found
Whereas when I remove your line, no errors are generated. I did try moving it, but I still get this error.
do I need to modify another line?
thanks 
A backslash is missing at the end of the penultimate line.
Hello @VonOx
Ah yes, I could have seen it 
Thanks once again
Have a good day