Revert python default (#353)

* Updates for 3.0.0

 - Bump the base Alpine build back to latest
 - Set NodeJS 16 as default
 - Drop NodeJS 12
 - Add NodeJS 18

* Finish updating README.md

* Update default versions in custom build scripts

* Add 3.0.0-beta.1

* Merge 3.0.0 work into master (#317)

* 2.2.0-beta.1

* Updates for NR 3.0.0 release (#311)

* Updates for 3.0.0

 - Bump the base Alpine build back to latest
 - Set NodeJS 16 as default
 - Drop NodeJS 12
 - Add NodeJS 18

* Finish updating README.md

* Update default versions in custom build scripts

* Add 3.0.0-beta.1

* Bump to 3.0.0-beta.2

* Bump dev to 3.0.0-beta.3 (#314)

* Remove Python 2 (#315)

* Bump dev to 3.0.0-beta.3

* Remove Python2 from alpine builds

* Bump to 3.0.0-beta.4 (#316)

* Bump to 2.1.6

* Bump to 2.2.0

* Bump to 2.2.1

* Updates for 3.0.0

 - Bump the base Alpine build back to latest
 - Set NodeJS 16 as default
 - Drop NodeJS 12
 - Add NodeJS 18

* Bump to 3.0.0-beta.4

* Remove new empty line

Co-authored-by: knolleary <[email protected]>

Co-authored-by: Nick O'Leary <[email protected]>
Co-authored-by: knolleary <[email protected]>

* Bump to 3.0.0 (#318)

Co-authored-by: knolleary <[email protected]>

* Add PubkeyAccessKeyTypes settings (#323)

* Add PubkeyAccessKeyTypes settings

* Add PubkeyAccessKeyTypes settings

* Add ssh fix to debian based build

* New entrypoint (#324)

* Add PubkeyAccessKeyTypes settings

* Switch entrypoint to allow NR to run as root if needed

This works round npm droping uid when running as root

* Bump to 3.0.1

* First pass at fix for #326 (#327)

Fix for #326

* Bump to 3.0.2

* Fix NODE_OPTIONS (#334)

Thanks to @twocolors for finding this, applying from my id as having problems with easycla

* Set python3 to be the default python for npm (#336)

* Add stable release tag (#342)

* Add a stable tag

All 3.0.x will be tagged as nodered/node-red:3.0
All 3.1.x will be tagged as nodered/node-red:3.1

* Calculate Stable version rather than hard code it

* Fix passing cli args to Node-RED (#349)

The new entrypoint introduced #324 does not forward arguments to Node-RED. (which is a breaking change from 3.0.0)

With this change the old behavior is restored and one can override settings via the docker command again.

* Set version to 3.1.0-beta.1

* Revert setting default python

npm v9 removes the ability to set this (why?)

fixes #352

---------

Co-authored-by: Nick O'Leary <[email protected]>
Co-authored-by: knolleary <[email protected]>
Co-authored-by: NodeREDBot <[email protected]>
Co-authored-by: Dominik Schmidt <[email protected]>

Author: 4 people

.docker/Dockerfile.alpine

@@ -82,7 +82,6 @@ RUN chown -R node-red:root /usr/src/node-red && \
     rm -r /tmp/*
 
 RUN npm config set cache /data/.npm --global
-RUN npm config set python `which python3` --global
 
 USER node-red
 

.docker/Dockerfile.debian

@@ -80,7 +80,6 @@ RUN chown -R node-red:root /usr/src/node-red && \
     rm -r /tmp/*
 
 RUN npm config set cache /data/.npm --global
-RUN npm config set python `which python3` --global
 
 USER node-red
 

docker-custom/Dockerfile.custom

@@ -80,7 +80,6 @@ RUN chown -R node-red:root /usr/src/node-red && \
     rm -r /tmp/*
 
 RUN npm config set cache /data/.npm --global 
-RUN npm config set python `which python3` --global
 
 USER node-red
 

docker-custom/Dockerfile.debian

@@ -81,7 +81,6 @@ RUN chown -R node-red:root /usr/src/node-red && \
     rm -r /tmp/*
 
 RUN npm config set cache /data/.npm --global
-RUN npm config set python `which python3` --global
 
 USER node-red