Error: could not get uid/gid #3
Comments
|
Today I upgraded to node v0.10.26, Installed via node.js ppa I'm running on linux-mint 13.10 xfce x64. I get the same error when running as root
|
|
Caused by 2d701a8. Reverted, pushing a new npm now. Sorry about this. |
|
I wasn't able to upgrade to 0.0.5 becuase I made a quick temporary fix: Now Thanx |
|
@IlanFrumer see also - https://gist.github.com/isaacs/9117286 Via twitter:
|
|
@danmactough Thanx. |
|
Updated https://gist.github.com/isaacs/9117286 with annotations about what each line does. @IlanFrumer Yes, that will work, but it depends on having a specific root dir, and if uid-number ever has incompatible changes, it could break stuff. Better to fetch the exact version (and check the shasum while we're at it) and then move into the exact place that npm was installed. |
Unfortunately the script not working for me.. root=undefined? |
|
Ack, it should be |
|
I'm reopening this 'cause I've the same error (for different reasons). npm output: looking at that, I saw an and here last lines of strace: ps. don't know if this is the right place for this |
|
@lesion Same when running a raspian docker container through qemu-user-static (so emulating an armv7l machine). I worked around this by hard-coding for my target user (root) inside the container: Maybe |
|
@skl: I have the same use case, |
|
Same, building Mastodon in Docker, I used the |
|
We are still experiencing these errors in node alpine for M5 instances in AWS.
|
|
i got this issue moving from docker image mhart/alpine-node:10.6.0 to mhart/alpine-node:10.7.0 |
|
@isaacs any comments on this issue? are you guys planning to investigate this issue? @shavo007 both of your images fail in a EC2 M5 instance. Details here:
|
|
Interesting @raulgomis. I rolled back my version on a build agent and it worked... |
Relate-to: npm/uid-number#3 Change-Id: I71786586ab3cb4c7b92e08ff962a1fbec1895a35 Signed-off-by: Philippe Coval <p.coval@samsung.com>
|
Watching this issue. have same problem |
|
How can such a high severity bug STILL NOT BE FIXED on LTS?? |
|
Experiencing this behaviour in an official Docker container |
|
We also have the issue when building with Gitlab CI. 😕 |
|
also have that issue in |
|
I've opened a fresh issue to add visibility: #7 |
|
Same issue with alpine:latest, on arm64 |
|
Also happening with node:8-alpine |
|
Facing this on node:8-alpine. Interestingly enough, it cropped up a few months ago in one particular npm project, and adding |
|
Confirmed Using node:10.15.0-alpine in the Dockerfile, with an Amazon EC2, there is the UID error. |
|
Notice the word "unsafe" in the workaround under discussion. Gives me the creeps. So I prefer something like this: That way we allow the unsafe operation where we really need it, then go back to normal sane mode. |
Damn and blast, didn't think of that. Going to push this out right away. Thanks! |
|
After all, |
|
For me, the workaround worked, but it doesn't seem to be a very reliable solution tbh... |
|
Same issue on |
|
This issue just happened to me as well on npm install -g nodemon with this image. |
|
Not sure why this issue hasn't been addressed yet after 4 years. Is this just a spare-time hobby project for NPM or something? |
|
not sure how why was it closed and not reopened again after so much time : |
|
Same here, ran into this issue with node:10-alpine and node:11-alpine. Got it fixed with the "workaround" above. |
Started hitting this issue npm/uid-number#3. Seems to be related to how this different CI system is building the container. Docs for this option can be found: https://docs.npmjs.com/misc/config. I don't see any security risks here since we are docker multi-container building and yanking out files from the initial node build.
Started hitting this issue npm/uid-number#3. Seems to be related to how this different CI system is building the container. Docs for this option can be found: https://docs.npmjs.com/misc/config. I don't see any security risks here since we are docker multi-container building and yanking out files from the initial node build.
Started hitting this issue npm/uid-number#3. Seems to be related to how this different CI system is building the container. Docs for this option can be found: https://docs.npmjs.com/misc/config. I don't see any security risks here since we are docker multi-container building and yanking out files from the initial node build.
npm config set unsafe-perm true is called otherwise we get
Error: could not get uid/gid
[ 'nobody', 0 ]
at .../uid-number/uid-number.js:37:16
...
error.
|
Still seeing this. |
Can confirm - Our |
|
This issue is 5 years old. Unless you haven't updated your systems since 2014, whatever you're seeing, it's not "the same" issue, even if it's similar error message text. I know it's easier to just post a new comment on an existing thread. But I need you to create a new issue. Please include the version of npm that you are using, any debug log file that was generated, and the command that you're running. Thanks. |
and others
This error was initially reported here: npm/npm#4719
I compiled and installed node 0.10.26 on Ubuntu 12.04; npm update dies:
Trying as non root a
sudo npm update -gyields the same error, only difference is[ 'nobody', 1000 ]instead of[ 'nobody', 0 ]The only way I could quickly get around was to comment out the error check (line 36), which I guess is not the proper way to do it.
The text was updated successfully, but these errors were encountered: