-
Notifications
You must be signed in to change notification settings - Fork 4
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
spawn EACCES error #4
Comments
Looks like you are trying to download a file that isn't there. Make sure you use |
Hi everyone, I also have the same problem of @carboni09 ... how can I solve it? @prescottprue i use os.tmpdir() |
@samirlegdah do you have any modifications in the code presented in this repo? |
Same thing happening right here. How can I fix this problem? I am using os.tmpdir() as suggested. Any help is greatly appreciated! |
Were you able to figure it out? I am facing the same issue, and i cant figure it out |
I never figured it out. I ended up using a vm to get this to work. From cloud functions now I call the service on the vm that returns the image. |
I also switched to using a VM, but recently have been working with Cloud Run which supports Docker images. FWIW, here is the Dockerfile we are using:
|
Try to change executablePath to .executablePath('gs') as mentioned here: https://stackoverflow.com/questions/50816826/error-cloud-functions-for-firebase-spawn-eacces-ghostscript It works for me. |
Here's is the error I get when I deploy and run it.
"@google-cloud/storage": "^1.3.1",
"firebase-admin": "~5.4.0",
"firebase-functions": "^2.0.2",
exception: { Error: spawn EACCES at exports._errnoException (util.js:1020:11) at ChildProcess.spawn (internal/child_process.js:328:11) at exports.spawn (child_process.js:370:9) at Object.exec (/user_code/node_modules/gs/index.js:86:28) at /user_code/index.js:43:7 at bucket.file.download.then (/user_code/index.js:33:11) at process._tickDomainCallback (internal/process/next_tick.js:135:7) code: 'EACCES', errno: 'EACCES', syscall: 'spawn' }
The text was updated successfully, but these errors were encountered: