-
Notifications
You must be signed in to change notification settings - Fork 72
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
Unable to execute in postinstall script in yarn monorepo #126
Comments
I don't have any experience with Docker unfortunately. Is this a Docker-specific issue or can you reproduce this outside of Docker? |
I doubt it's a docker-specific issue. More accurately, the issue could be described as My initial guess is that the issue has something to do with yarn workspaces on linux interfering with the If you have a way of testing this on Linux and can put some time into doing so, I can try and throw together a repo that can minimally reproduce the issue. I might also find out more about the issue as I do so. |
I use Fedora 27, and it works well here. If you can tell me how to reproduce on Debian, I'm willing to put together a VM to test. |
I've edited the issue title to reflect these points and have created a minimal repro case. To test this, you'll need to install yarn and run |
Thank you @chrbala I will take a look at it but unfortunately I don't have experience with Yarn either. As far as I understand Does Yarn work correctly with other native modules? If yes, we should take a look at how their |
I am having the same issue on Ubuntu 16.04 (Debian based though not sure it matters) and I get different behavior across different cloud hosts. On Digital Ocean the issue occurs if I build the project as root, but not as a newly created user. On AWS, I get the issue with the non root user using the same script that works on Digital Ocean. The project in question is: https://github.com/nimiq-network/core and it does indeed use Yarn. |
I cd'ed to |
@emkman Can you give the exact steps to reproduce your problem? And what environment you ran? |
I played around with |
Sure, thank you for your effort tracking it down. |
Yeah, feel free. It looks like it affects all of the native modules on yarn
monorepos. I changed my installation workflow to make this work.
…On Mon, May 21, 2018 at 09:54 Ethan Kravitz ***@***.***> wrote:
Sure, thank you for your effort tracking it down.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#126 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGhKdEMFrKcBc6aCf1WxVQa6Xierpzrdks5t0uNMgaJpZM4TfN8W>
.
|
@chrbala Can you share with us what the workaround was, in that yarn bugreport? |
When I try to install node-lmdb on linux, I get the following error:
But when I run
find . -name "node-lmdb.node"
, I get.I'm happy to provide a docker file or share the container if it's useful.
The text was updated successfully, but these errors were encountered: