Repository navigation
[BUG] Failed to install npm package from git in docker since v6.11.0 #624
Description
What / Why
This bug is related to #476 (comment) and #514
When
npm install packages from git in docker
Where
- packages from public git repositories
How
Current Behavior
# npm i
npm ERR! code 128
npm ERR! Command failed: git clone --depth=1 -q -b v2.0.5 git:https://github.com/boblauer/MockDate.git /root/.npm/_cacache/tmp/git-clone-c9699b7f
npm ERR! fatal: could not create leading directories of '/root/.npm/_cacache/tmp/git-clone-c9699b7f': Permission denied
npm ERR!
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-12-23T09_49_05_990Z-debug.log
Steps to Reproduce
- Create simple package.json with git dependency
{
"name": "test-npm",
"dependencies": {
"mockdate": "git:https://github.com/boblauer/MockDate.git#v2.0.5"
}
}
- run
docker run --network=host -it -v $(pwd):/var/work/test -w /var/work/test node:12.14.0 /bin/bash ls -lshows that files are owned by unknown user and unknown group (this is typical behaviour on build agents like teamcity, teamcity clones git repo and mounts it inside docker container)
# ls -l
-rw-r--r-- 1 20857 115755 114 Dec 23 09:46 package.json
- run
npm install
# Depends on environment you can get
npm ERR! code 128
npm ERR! Command failed: git clone --depth=1 -q -b v2.0.5 git:https://github.com/boblauer/MockDate.git /root/.npm/_cacache/tmp/git-clone-c9699b7f
npm ERR! fatal: could not create leading directories of '/root/.npm/_cacache/tmp/git-clone-c9699b7f': Permission denied
npm ERR!
# or
npm ERR! Error while executing:
npm ERR! /usr/bin/git ls-remote -h -t ssh://git@<private server>/admin-template.git
npm ERR!
npm ERR! No user exists for uid 1000
npm ERR! fatal: Could not read from remote repository.
- run
npm i -g npm@6.10(downgrade to npm 6.10.X) - run
npm install
# all works well!
updated 1 package and audited 1 package in 1.355s
found 0 vulnerabilities
Expected Behavior
npm install/npm ciworks well like npm@6.10
Activity
SabatierBoris commentedon Dec 23, 2019
I have the same issue with npm 6.13.4.
It's working with npm 6.4.1
doochik commentedon Dec 28, 2019
@isaacs please, take a look on this
isaacs commentedon Dec 30, 2019
Is the npm command being run as root, or some other user?
I'd like to try to zoom in on the problem and leave the docker aspect out of it.
If I understand this correctly:
npm installis root$HOMEdirectory is/rootor some other root owned directory$HOME/.npmis root-owned.Simpler reproduction, sans docker:
I will take a look today and see how hard this'll be to fix.
isaacs commentedon Dec 30, 2019
Note for myself and @npm/cli-team: this problem does not occur with pacote v10, so it's strictly a pacote v9 issue.
To verify this, I applied this diff to pacote:
(This is required because otherwise pacote v10 will try to fetch github repos from their static tarball endpoint, as that's usually much faster.)
Then ran:
fix(git): Do not drop uid/gid when executing in root-owned directory
fix(git): Do not drop uid/gid when executing in root-owned directory
isaacs commentedon Dec 30, 2019
Looks like npm/pacote#26 will fix this problem, assuming that I am understanding the root cause. (At the very least, it fixes a problem, which is that running
npm installof a git dep as a root user with a root-owned npm cache will not fail, and it seems like that's the thing happening here.)fix(git): Do not drop uid/gid when executing in root-owned directory
doochik commentedon Dec 31, 2019
Yes, npm install is being run as root.
Thanks for the fix!
simonkotwicz commentedon Feb 19, 2020
@isaacs Installing npm packages from git private repositories in docker still fails (since v6.11.0 and still fails with 6.13.6) when using a ~/.netrc file or ~/.git-credentials file
isaacs commentedon Feb 26, 2020
@simonkotwicz That's a different issue. Can you please post a new issue describing the situation, ideally with a more fleshed-out reproduction case?
simonkotwicz commentedon Feb 26, 2020
opened #950
augnustin commentedon Mar 23, 2021
Using npm in a docker, the issue still occurs to me.
With:
Any idea?
kowalk commentedon Mar 29, 2021
same here ;/
12 remaining items
eisenyang commentedon Aug 22, 2021
I run into this error, Then I tried yarn, it worked.
goncalves-diogo commentedon Aug 31, 2021
Hi, I've also come across the same error, If you look deeper into the logs you can see that the issue lies on the
_cacachedirectory. NPM doesn't have permission to write into it. In my case, It was trying to write to the folder on/root/.npm/_cacachewhich isn't really a good idea because it's root.That being I think there are two possible temporary solutions to this problem:
sudo chown -R 1000:1000 /current/cache/folder(If this folder is root, don't do it)npm config set cache ~/random/place --global. (NOTE: It might be required to do step 1 with the new repository).eMPee584 commentedon Oct 19, 2021
Good idea, but with
/tmp/npm.cacheat 777 permissions, it will still throw the same problem..Also, because I was running under
sudo, I tried prependingenv -ito not forwardSUDO_UIDvariable, but that doesn't fix it either.likemusic commentedon Oct 30, 2021
If run manually run
git --no-replace-objects clone https://git@github.com/likemusic/date-parse-multiformats.git /root/.npm/_cacache/tmp/git-cloneMplQnl --recurse-submodules --depth=1it works as expected without any errors.Try no sudo to avoid npm/cli#624
Fix Ubuntu 20.04 test runner installation of SDPoker
Fix Ubuntu 20.04 test runner installation of SDPoker (#218)
wongjiahau commentedon Jan 3, 2022
I'm facing this issue when trying to install from a Gitlab private repo using HTTPS with
node@16.13.1andnpm@8.3.0. Things worked when I downgraded npm as per #624 (comment).likemusic commentedon Jan 3, 2022
When I previously post log for issue I investigated the problem.
This happens bacuase npm tries to clone (
git clonesubprocess) in temp directory for current user but it runs as current directory owner user wherenpmruns.In my case the owner of directory was
nodebut I run npm as root user. So npm start process as root-user (because I run it as root user), but whengit clonesupbrocess runs it tries clone in temp directory for root user asnodeuser whose haven't enough rigth to create subdirectories duringgit clone.To prevent this issue (untill it would be fixed) you must run
npmcommand as user who is current directory owner, for example:Or change owner for current directory:
wongjiahau commentedon Jan 3, 2022
@likemusic For my case the directory that contains
package.jsonis in fact not owned byroot, and after doingchown root:root .the problem is fixed indeed. Thanks!murtycodes commentedon Jun 14, 2022
This worked for me:
RUN apk add --no-cache githttps://stackoverflow.com/a/63033749/6884069
[Fix]: Publish the package on NPM
georgisoft2020 commentedon Oct 31, 2022
When there is a reference to a git library in package json, like :
git://it really shows the error :npm ERR! No user exists for uid 1000That's why for me a workaround was to use the command npm install with other user inside docker container.
First check what users do you have on that docker with the help of
cat /etc/passwd, then use an user different from root.runuser -u otheruser -- npm installFix random failed to install npm package from git in docker
chore: release versions (npm#624)