[ERROR] Node.js setup_16.x | bash - on Debian Installation wrong version 18.x #1583
Comments
|
hello, |
|
We're having the same issue with our Ruby Node image. Node 18 is installed with breaking changes. Any suggested fix? |
Thank you antocorso, I switched to nvm source for node 16 it works. But the issue in this case is still there. |
We have to switch to another source using NVM to install 16. ref: https://deb.nodesource.com/setup_16.x this source with a wrong version, I think they may not support 16 anymore here. Still waiting for response. |
|
You're a legend @liang611zh |
also changed shell to bash We use nvm to install Node.js as nodesource distributions somehow always install Node.js 18 instead (see nodesource/distributions#1583)
|
This issue seems to be a duplicate of #1579, see #1579 (comment) tl;dr You have to pin echo "Package: nodejs
Pin: origin deb.nodesource.com
Pin-Priority: 600" > /etc/apt/preferences.d/nodesource |
Thank you o1y, I saw your issue before I open this issue. In my case the 'Pin' is not work, but I think your suggestion will help others who have the same problem. |
|
After adding the nodesource repository, can you check the output from |
* Use npm audit to update npm packages * Use Node.js version 16 in Docker development also changed shell to bash We use nvm to install Node.js as nodesource distributions somehow always install Node.js 18 instead (see nodesource/distributions#1583) * Use node after installation * Split installation of Node.js to multiple RUN commands Also alias the default version If you want to see the full output during Docker build, you can use the "--progress=plain" option. * Uniy sass packages and update yarn lock * Reflect changes in production and test Dockerfiles * Add comments to Dockerfile and tighten run commands * Add sass-loader back as dependency * Switch back to old version of sass-loader This is because we still use webpacker v4 currently. We will upgrade this depenedency when we switch from @rails/webpacker to webpack in the future. * Use "-no-install-recommends" for yarn install in prod This is so that Node.js is not installed again, which would result in v18, which we don't want at the moment. * Use consistent ${} syntax in Dockerfile & fix Node path * Copy Node.js over to /usr/local This ensures that the app user can access node that was previously installed with nvm in /root/.nvm * Apply quote arguments suggestion (in code review) Co-authored-by: Christian Heusel <christian@heusel.eu> * Quote arguments in other Dockerfiles as well * Replace deprecated apt-key and improve Dockerfiles - Replaced Yarn installation with "corepack", a new binary shipped with Node.js starting with v16. This also means that Yarn is upgraded from v1 to v2 with a different CLI, e.g. we now use "yarn workspaces focus" instead of "yarn install" to install the dependencies for the workspace in the current working directory. - Update GPG key handling during PostgreSQL installation - Added some more comments to the Dockerfile - Moved copying of Node.js up in the Dockerfile More yarn-related changed in subsequent commits. * Upgrade to Yarn 2 and add packages for non-error webpack build * Copy Yarn to usr folder alongside other Node.js tooling * Activate Yarn for app user * Only copy node over to usr folder * Go back to Yarn1 and explicitly set Yarn version - Added a fix so that corepack really installs the version we want and not some other old version - with Yarn2+, building curerntly fails, so we switch back to Yarn1 and deal with an upgrade of Yarn in the future * Remove ".yarn" from .gitignore Yarn1 does not generate this folder * Remove unnecessary dependencies from package.json "unnecessary" means dependencies that were added when trying out Yarn2+ * Add back missing "--production=false" to "yarn install" * Use "ruby:3.1.4-bullseye" to have PostgreSQL available * Add missing `apt update` in dev and test Dockerfiles Co-authored-by: Christian Heusel <christian@heusel.eu> * Group `update` and `install` in one RUN statement (in prod Dockerfile) * Remove superfluous newline * Make Node.js version logging one RUN statement * Explicitly set `--production=true` during `yarn install` --------- Co-authored-by: Christian Heusel <christian@heusel.eu>
* Use npm audit to update npm packages * Use Node.js version 16 in Docker development also changed shell to bash We use nvm to install Node.js as nodesource distributions somehow always install Node.js 18 instead (see nodesource/distributions#1583) * Use node after installation * Split installation of Node.js to multiple RUN commands Also alias the default version If you want to see the full output during Docker build, you can use the "--progress=plain" option. * Uniy sass packages and update yarn lock * Reflect changes in production and test Dockerfiles * Add comments to Dockerfile and tighten run commands * Add sass-loader back as dependency * Switch back to old version of sass-loader This is because we still use webpacker v4 currently. We will upgrade this depenedency when we switch from @rails/webpacker to webpack in the future. * Use "-no-install-recommends" for yarn install in prod This is so that Node.js is not installed again, which would result in v18, which we don't want at the moment. * Use consistent ${} syntax in Dockerfile & fix Node path * Copy Node.js over to /usr/local This ensures that the app user can access node that was previously installed with nvm in /root/.nvm * Apply quote arguments suggestion (in code review) Co-authored-by: Christian Heusel <christian@heusel.eu> * Quote arguments in other Dockerfiles as well * Replace deprecated apt-key and improve Dockerfiles - Replaced Yarn installation with "corepack", a new binary shipped with Node.js starting with v16. This also means that Yarn is upgraded from v1 to v2 with a different CLI, e.g. we now use "yarn workspaces focus" instead of "yarn install" to install the dependencies for the workspace in the current working directory. - Update GPG key handling during PostgreSQL installation - Added some more comments to the Dockerfile - Moved copying of Node.js up in the Dockerfile More yarn-related changed in subsequent commits. * Upgrade to Yarn 2 and add packages for non-error webpack build * Copy Yarn to usr folder alongside other Node.js tooling * Activate Yarn for app user * Only copy node over to usr folder * Go back to Yarn1 and explicitly set Yarn version - Added a fix so that corepack really installs the version we want and not some other old version - with Yarn2+, building curerntly fails, so we switch back to Yarn1 and deal with an upgrade of Yarn in the future * Remove ".yarn" from .gitignore Yarn1 does not generate this folder * Remove unnecessary dependencies from package.json "unnecessary" means dependencies that were added when trying out Yarn2+ * Add back missing "--production=false" to "yarn install" * Use "ruby:3.1.4-bullseye" to have PostgreSQL available * Add missing `apt update` in dev and test Dockerfiles Co-authored-by: Christian Heusel <christian@heusel.eu> * Group `update` and `install` in one RUN statement (in prod Dockerfile) * Remove superfluous newline * Make Node.js version logging one RUN statement * Explicitly set `--production=true` during `yarn install` --------- Co-authored-by: Christian Heusel <christian@heusel.eu>
|
Looks we found solution to help people who have the same issue. |
Describe your bug
When install node in our pipline, we got a wrong version of node.
Distribution Information:
docker : php 8.1
Node Version:
To Reproduce
Steps to reproduce the behavior:
curl -sL https://deb.nodesource.com/setup_16.x | bash -apt-get -y install nodejsnode -vExpected behavior
A clear and concise description of what you expected to happen.
By using the same script.
Before Jun 15 our pipline will install correct version 16.x,
but yesterday this script will install a wrong version 18.x which caused the build process failed.
Screenshots
If applicable, add screenshots to help explain your problem.
The text was updated successfully, but these errors were encountered: