Unable to run the the jsreport-aws-lambda-starter-kit on AWS Node.js 10 runtime.
I was trying to bring up a jsreport lamba as per the guidelines provided in the https://github.com/jsreport/jsreport-aws-lambda-starter-kit. This works fine when I use the aws Node.js 8.10 run time. But stops working when I switch to the AWS recommended Node.js 10 run time. Had a done a bit of research on this but nothing really helped. Please help me here if there is way to achieve it or if it already discussed here.
This is the error troubling me all the time with AWS Node.js 10.x run time.
"errorMessage": "Failed to launch chrome!\n/tmp/headless-chromium: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory\n\n\nTROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md\n",
"Error: Failed to launch chrome!",
"/tmp/headless-chromium: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory",
" at onClose (/var/task/node_modules/puppeteer/lib/Launcher.js:360:14)",
" at Interface.helper.addEventListener (/var/task/node_modules/puppeteer/lib/Launcher.js:349:50)",
" at Interface.emit (events.js:203:15)",
" at Interface.EventEmitter.emit (domain.js:448:20)",
" at Interface.close (readline.js:397:8)",
" at Socket.onend (readline.js:173:10)",
" at Socket.emit (events.js:203:15)",
" at Socket.EventEmitter.emit (domain.js:448:20)",
" at endReadableNT (_stream_readable.js:1143:12)",
" at process._tickCallback (internal/process/next_tick.js:63:19)"
Thanks in advance,
You probably need to compile the headless chrome for the particular amazon linux os used in the lambda nodejs 10 runtime.
Maybe you find notes on how to do it here. However, it is likely quite challenging.
Thanks @jan_blaha , let me give it a try if it helps.
Hi @renjuthomaz did you have luck finding the solution to this problem ?
Hi, any news regarding this?
You can check this PR. There seems to be some very recent progress.
I reworked the starter kit to use a different chrome package which has no issues with nodejs 12.x runtime and also use lambda layers.
the relevant documentation can be found here at this moment