-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Openshift installation permission errors #721
Comments
This looks like an Openshift permissions problem - see also nodejs/node-gyp#959 Sometimes |
Just tried that with no luck ... |
@jchapelle Were you able to make any progress? |
Hello,
Thanks for the contact.
I actually couldn't make any progress.
The application is deployed in openshift but I still got a list of errors
during each deployment
…On Mon, Mar 27, 2017 at 9:38 PM, Lovell Fuller ***@***.***> wrote:
@jchapelle <https://github.com/jchapelle> Were you able to make any
progress?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#721 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AF4GXasL_IwdyMiQ6-EgwTpcU_48epRgks5rqBAngaJpZM4MJ4S1>
.
--
Jean Chapelle
|
@jchapelle Thanks for the update. Let's leave this open in case others with more experience of Openshift can help. |
Great thanks
…On Mon, Mar 27, 2017 at 11:37 PM, Lovell Fuller ***@***.***> wrote:
@jchapelle <https://github.com/jchapelle> Thanks for the update. Let's
leave this open in case others with more experience of Openshift can help.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#721 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AF4GXbwx5FT2FzCEuNITp3JItuZzWU3Dks5rqCw2gaJpZM4MJ4S1>
.
--
Jean Chapelle
|
Possibly related sources of help: |
I'm going to close this as there have been no further reports of what appears to be a permissions problem specific to Openshift and/or node-gyp. |
Installation of sharp on openshift fails because user does not have permission to access the dev dir.
The text was updated successfully, but these errors were encountered: