-
Notifications
You must be signed in to change notification settings - Fork 12k
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
Infinite Loop with Docker / npm -g install @angular/cli
#7389
Comments
Having same issue. |
I am also having the same issue. |
Same here |
workaround is here: nodejs/node-gyp#1236 (comment) |
Okay the nodejs/node-gyp#1236 trick/workaround seems to fix it:
|
Node Sass could not find a binding for your current environment: Linux 64-bit with Node.js 8.x Found bindings for the following environments:
when I am running when I try to launch ng tests using PhantomJS I get the above error? anyone able to shed some light on why? or how I can resolve it I attempted node-sass rebuild and that did not work |
Same here. What I don't get is why there's no problem of user when using node 7.9.0. For now, i'm keeping node 7.9.0. |
Same here! |
Same here, and I'm not using Docker on this project, but it is installed on my machine. Angular-cli should have installed as root:root drwxr-xr-x 8 root root 4096 Nov 4 17:06 ./ drwxr-xr-x 5 root root 4096 Nov 3 16:02 ../ drwxr-xr-x 3 root root 4096 Nov 4 15:58 @angular/ drwxr-xr-x 14 nobody stephen 4096 Nov 3 16:02 angular-cli/ drwxr-xr-x 7 root root 4096 Nov 4 17:06 firebase-tools/ drwxr-xr-x 12 nobody stephen 4096 Nov 3 16:12 npm/ drwxr-xr-x 3 root root 36864 Nov 4 17:06 .staging/ drwxr-xr-x 9 root root 4096 Nov 4 15:40 webpack/ This fixed it though: |
Upgrading Node (fixes #762) Issue with insufficient directory permissions see: angular/angular-cli#7389
Same on MacOS High Sierra (node v8.9.4 and npm 5.6.0) below statement looping for more than 2 hours now.. Just exited out of installation using Control+C and ng -v works fine :) |
This bug is still reproducible on For those coming from google to quickly get around this use this command to install:
the |
I see that this thread is now closed. Has there been an actual fix or is everyone still just using the --unsafe command? I got a similar error when installing today. The unsafe command fixed the infinite loop issue for me as well. |
Actually, if you just control c out of the loop, you'll see that angular cli is installed. |
Still getting this in March 2018: FROM node:8.0
RUN npm install -g @angular/cli This spins into an infinite loop when in gets to the Why is this still a problem? |
Same issue with Node v9.11.1 and NPM 5.6.0 |
Tried installing this with the latest Node docker image. Received the loop because it didn't want to install as root. Use the |
npm_config_user=root npm install -g ... works for me |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Bug Report or Feature Request (mark with an
x
)Versions.
Node v8.3.0
NPM v5.3.0
OS: Docker
buildpack-deps:jessie
Repro steps.
docker build
The log given by the failure.
...repeating infinitely...
Note
RUN npm install -g node-gyp
seems to work fine.Desired functionality.
Installs properly
Mention any other details that might be useful.
N/A
The text was updated successfully, but these errors were encountered: