attack-navigator
attack-navigator copied to clipboard
Running Error - Step 8/11 : RUN npm install --unsafe-perm
Step 8/11 : RUN npm install --unsafe-perm ---> Running in ac292f6fe2fb
npm notice
npm notice New minor version of npm available! 8.15.0 -> 8.19.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.19.0
npm notice Run npm install -g [email protected]
to update!
npm notice
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @angular-devkit/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/karma
npm ERR! dev karma@"~5.0.0" from the root project
npm ERR! peer karma@"*" from [email protected]
npm ERR! node_modules/karma-jasmine
npm ERR! dev karma-jasmine@"~4.0.0" from the root project
npm ERR! peer karma-jasmine@">=1.1" from [email protected]
npm ERR! node_modules/karma-jasmine-html-reporter
npm ERR! dev karma-jasmine-html-reporter@"^1.5.0" from the root project
npm ERR! 1 more (karma-jasmine-html-reporter)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional karma@"~5.1.0" from @angular-devkit/[email protected]
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR! dev @angular-devkit/build-angular@"~0.1100.3" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/karma
npm ERR! peerOptional karma@"~5.1.0" from @angular-devkit/[email protected]
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR! dev @angular-devkit/build-angular@"~0.1100.3" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /root/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2022-09-01T10_46_17_505Z-debug-0.log
The command '/bin/sh -c npm install --unsafe-perm' returned a non-zero code: 1
Hello,
I have the same issue, any update on this?
Can confirm this issue while trying to use docker.
@seansica will you please look into this and investigate what is going awry with the Docker build?
Using node:14 instead of 16 fixed the docker build.
I just accepted @seansica's pull request which addresses the issue a different way - by tacking on --legacy-peer-deps
to the npm install
command. This fix is in the develop branch for now, so it will be included in the next release. I'll keep this issue open until then.