Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

npm install failure on Ubuntu Helix webassembly Dockerfiles #1324

Closed
mthalman opened this issue Jan 15, 2025 · 1 comment · Fixed by #1325
Closed

npm install failure on Ubuntu Helix webassembly Dockerfiles #1324

mthalman opened this issue Jan 15, 2025 · 1 comment · Fixed by #1325

Comments

@mthalman
Copy link
Member

Failure occurs on the following Dockerfile lines:

#7 [4/7] RUN npm install -g npm
#7 0.819 npm ERR! code EBADENGINE
#7 0.820 npm ERR! engine Unsupported engine
#7 0.821 npm ERR! engine Not compatible with your version of node/npm: [email protected]
#7 0.821 npm ERR! notsup Not compatible with your version of node/npm: [email protected]
#7 0.821 npm ERR! notsup Required: {"node":"^20.17.0 || >=22.9.0"}
#7 0.821 npm ERR! notsup Actual:   {"npm":"9.8.1","node":"v18.18.2"}
#7 0.823 
#7 0.823 npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2025-01-15T06_37_14_368Z-debug-0.log
#7 ERROR: process "/bin/sh -c npm install -g npm" did not complete successfully: exit code: 1
@mthalman
Copy link
Member Author

This is caused by a new version of NPM (version 11) being released. It requires Node 20+ but Node 18 is currently installed. We could update the npm install -g npm command to target NPM 10 so that it's compatible with Node 18. But since Node 18 is EOL in 3 months, it doesn't make much sense to cater to that version and instead just upgrade Node to a newer version.

@mthalman mthalman changed the title npm install failure on Ubuntu Helix Dockerfiles npm install failure on Ubuntu Helix webassembly Dockerfiles Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant