ddev: Unable to start DDEV with `nodejs_version: 18` (upstream problem, fix with nodejs 16)
Is there an existing issue for this?
- I have searched the existing issues
Run a Diagnostic and Paste Link Here
No response
Expected Behavior
For startup to succeed without fail.
Actual Behavior
Preparing to unpack .../nodejs_18.14.0-deb-1nodesource1_amd64.deb ...
Unpacking nodejs (18.14.0-deb-1nodesource1) ...
Setting up nodejs (18.14.0-deb-1nodesource1) ...
npm ERR! `unsafe-perm` is not a valid npm option
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2023-02-06T18_20_13_278Z-debug-0.log
ERROR: executor failed running [/bin/sh -c bash /tmp/setup_node.sh && apt-get install nodejs && npm config set unsafe-perm true && npm install --global gulp-cli yarn]: exit code: 1
------
> [drud/ddev-webserver:v1.21.4-houston-built 9/12] RUN bash /tmp/setup_node.sh && apt-get install nodejs && npm config set unsafe-perm true && npm install --global gulp-cli yarn:
Steps To Reproduce
- ddev version v1.21.4
- Macbook M1 - OS X Ventura
- Github Actions
ubuntu-latest
- Ubuntu 22.04
In config.yaml:
type: drupal9
docroot: web
php_version: "8.0"
webserver_type: nginx-fpm
database:
type: mariadb
version: "10.3"
php_version: 8.1
nodejs_version: 18
Anything else?
This job used to succeed four days ago and started failing three days ago. I can confirm this in GIthub Actions as well as my local machine.
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 2
- Comments: 22 (9 by maintainers)
Commits related to this issue
- Pin to node 16 for now -- see https://github.com/ddev/ddev/issues/4614 — committed to palantirnet/drupal-10-development by agentrickard a year ago
Prerelease fixing this issue is available https://github.com/drud/ddev/releases/tag/v1.21.5-alpha1
Added a 4th option to the possibilities in https://github.com/drud/ddev/issues/4614#issuecomment-1419870911
I’ve been running HEAD since Monday and it’s been fine. I would lean towards towards #4. Make sure that the release notes indicate this is all changes and reflects the upcoming release, and then if you get feedback about bugs you could roll a hotfix only release but you’d have the benefit of the bug reports for the March release.
I was just able to replicate on my Mac after wiping my docker images completely - I must have had some dangling docker images I thought I’d removed.
This is certainly broken for node 18. Node 16 works correctly. As far as a hotfix goes, I guess it depends how many users you expect to be on node 18?
I think there might be a possible workaround that could be implemented with a
Dockerfile.pre.*