npm install from github fails with access permissions when using cache #263
This case is very Wercker focussed, but the Wercker CLI is thin Docker API client. I suspect that the root cause is somewhere in the Docker Mac file system layer.
Wercker CLI is a Docker API client to build and test your code using containers. You no longer need your dev tools on your host machine. The Wercker CLI downloads the Docker image, sets up the file systems and networking and starts the container. Using the
Here is the actual outcome:
As you can see, when running it with Docker on Linux, it works even when using packages from Github. With Docker Mac 1.12.0-beta22 (build 11222), using packages from Github fails with file system permission errors. Installing npm packages from npmjs.com was fixed via #76. I first thought this was another case of the same issue but @dsheets asked me to file a separate issue for this.
Here is the console output:
Steps to reproduce the behavior
The Wercker CLI uses a
and use the following NPM
What this basically does when running
This was referenced
Aug 13, 2016
There are potentially multiple issues here. The primary issue is the same issue is #117 --
Hi, Not sure I understand the work around, in our case it's NPM which creates a (.npm) directory on a mounted volume, when getting js packages. so npm changes the ownership of the files.
The permissions on this mounted volume is my own login on the Mac. So should a specific docker user, be the owner or be in the group? I am not aware of a 'docker' user anyways...
referenced this issue
Sep 15, 2016
This should be fixed in the just-released Beta 29. Sorry for the delay in resolving the issue -- we had a couple of false starts on the design but now we use an ACL entry to make xattrs (containing ownership metadata) behave like inode metadata in most circumstances. Please give it a try and let us know how it works (or doesn't) for you. I'm going to close this issue but if you find related problems, please feel free to re-open. If you find un-related problems, please open a new issue. :-)
Thanks for using Docker for Mac!