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
Within a docker build, Modules dependant on node-gyp fail (only where npm-shrinkwap in use) #1105
Comments
Maybe there are install scripts that start node-gyp, that's something a quick If that isn't it, you'll probably have more luck getting your question answered at https://github.com/npm/npm/issues. node-gyp's role is a passive one, it only does what it's told by the process that started it, presumably npm. |
node-gyp is being kicked off by a https://github.com/kesla/node-snappy I was able to get it to work by installing python, make and GCC as part of the docker build process, but it seems strange to me that this is necessary in this case |
My solution was to modify my docker image to install the dependancies of node-gyp: So that the node-gyp script could run. As to why the behaviour is different from the shrinkwrap non skrinkwrapped is still a bit of a mystery to me |
@vidhill Can you please provide your dockerfile I am constanly getting Gyp errors - sepecifally around Python paths. |
@vidhill I second this motion |
Hi, https://gist.github.com/vidhill/0a85dc1848feee4171944dc4d7757895 -this is an untested Dockerfile because I'm off to bed now.. |
Not sure which is the best place for this,
We are using a number of npm packages which in turn have a dependancy on node-gyp,
i.e. my project does not directly use node-gyp
We run npm-install as part of our docker image build process..
When I put a npm-shrinkwrap.json in place the npm install is failing due to errors relating to python not being in place..
Maybe I need to include a python install as part of pre-build
But my confusion is, why is would fail for this reason only when the npm-shrinkwrap is in place?
The text was updated successfully, but these errors were encountered: