Skip to content
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

Lambdas won't compile due to chmod in makedomainenv #7

Open
perlman opened this issue Feb 1, 2018 · 3 comments
Open

Lambdas won't compile due to chmod in makedomainenv #7

perlman opened this issue Feb 1, 2018 · 3 comments

Comments

@perlman
Copy link

perlman commented Feb 1, 2018

The chmod 077 lines prevent lambda from being build on the lambda build server. This was introduced with a7ef013.

Our solution was to remove the "chmod -R 077 *" lines, but I'm not sure of what context this was added. Perhaps 777 would be better?

@movestill
Copy link
Member

Our makedomainenv is running without issues on our lambda build server. What kind of error message are you getting?

@perlman
Copy link
Author

perlman commented Feb 1, 2018

We get a million "permission denied" errors when trying to compile a lambda. The cause is all of the files being owner unreadable. We spent a while trying to figure out why all of the files in the build environment had permission ----rwxrwx, and thus unreadable (and unexecutable). The simple fix was changing the chmod line to not strip owner access.

@movestill
Copy link
Member

movestill commented Feb 1, 2018

Ok looks like the chmod lines on the server aren't the same as what's in the commit. This was put in to reset the permissions when deploying from a Linux VM with shared folders on a Windows host.

perlman pushed a commit to neurodata/boss-manage that referenced this issue Feb 8, 2018
added subnet-f at the end of the subnet list.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants