-
Notifications
You must be signed in to change notification settings - Fork 44
Incorrect find usage in alpine #72
Comments
I'm running into this exact issue right now with
Installing postgresql-dev package did not resolve it for me |
I managed to resolve it with the following:
|
That makes sense. Alpine images are slimmed down to contain the bare minimum so they likely do not have any of the build tools needed to compile the native driver (i.e. g++ and the libpq headers). |
after this can be node_modules copied into another alpine linux ( e.g docker multistage builds) to not have all those apk dependencies required ? |
@lukasa1993 yes (try it!) |
Hi there, thanks for this thread everyone! This seems to be the only documentation available on the internet on how to get This is what worked for us: In the base image we have
and in the slimmed-down production stage of the the multi-stage image we then only need
So it works with less dependencies, but Note that this is tested through Slonik. Without Edit: I adjusted the code above to reflect the insights from below: In production only |
@jorinvo You shouldn’t need the full |
@charmander thank you for the reply! I tested it and, indeed, |
In alpine linux, used mostly for docker, Call to find failed, because in alpine find can't search in multiple locations.
It would be better to split find calls, like this:
Full log attached.had
The problem had gone after installing postgresql-dev package.
Steps to reproduce:
node_gyp_error.txt
The text was updated successfully, but these errors were encountered: