repository
repository copied to clipboard
Noudesource.com deprecation warning makes build slow
Overview
The current build process uses a script hosted in noudesource.com to install Node.js, which is deprecated, generates a warning, and adds a whole minute of wait to the build process:
#9 [4/4] RUN curl -fsSL https://deb.nodesource.com/setup_16.x | bash - && apt-get install -y nodejs && npm install --omit dev && pip install -r requirements.txt
#9 0.227
#9 0.227 ================================================================================
#9 0.227 ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
#9 0.227 ================================================================================
#9 0.227
#9 0.227 SCRIPT DEPRECATION WARNING
#9 0.227
#9 0.227
#9 0.227 This script, located at https://deb.nodesource.com/setup_X, used to
#9 0.227 install Node.js is deprecated now and will eventually be made inactive.
#9 0.227
#9 0.227 Please visit the NodeSource distributions Github and follow the
#9 0.227 instructions to migrate your repo.
#9 0.227 https://github.com/nodesource/distributions
#9 0.227
#9 0.227 The NodeSource Node.js Linux distributions GitHub repository contains
#9 0.227 information about which versions of Node.js and which Linux distributions
#9 0.227 are supported and how to install it.
#9 0.227 https://github.com/nodesource/distributions
#9 0.227
#9 0.227
#9 0.227 SCRIPT DEPRECATION WARNING
#9 0.227
#9 0.227 ================================================================================
#9 0.227 ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
#9 0.227 ================================================================================
#9 0.227
#9 0.227 TO AVOID THIS WAIT MIGRATE THE SCRIPT
#9 0.227 Continuing in 60 seconds (press Ctrl-C to abort) ...
#9 0.227
#9 60.23
#9 60.23 ## Installing the NodeSource Node.js 16.x repo...
This should be migrated to avoid breaking the build in the future and also to skip this 60 second wait.
It seems like a similar problem has happened before (#47), but new action is required.