serverless-chrome
serverless-chrome copied to clipboard
Get ready for Lambda running environment updates
AWS announced about changing running environment of Lambda.
There are two breaking changes:
- New
nodejs10.xruntime uses Amazon Linux 2 - Any other runtimes except
nodejs10.xwill be updated to use Amazon Linux 2018.03 release (from Amazon Linux 2017.03 release)
Please refer below links also:
- https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html
- https://aws.amazon.com/blogs/compute/upcoming-updates-to-the-aws-lambda-execution-environment/
According to @mhart's tweet, Amazon Linux 2018.03 based lambda runtime removed some deps including Perl and Dash. Here is a list of removed dependencies.
So we need to test serverless-chrome with updated runtime, and discuss about supporting amazonlinux2 based lambda runtime.
@mooyoul Good list, thanks for that. Besides the removed binaries/libs, I also couldn't locate any fonts.
https://github.com/alixaxel/chrome-aws-lambda/issues/37#issuecomment-493646469
If somebody can provide infrastructure to build binaries again (https://github.com/adieuadieu/serverless-chrome/issues/195) then changing runtime will not be a big issue, I guess.
@olecom What do you mean by infrastructure? I can provide access to a high-end server for a few hours if needed, I also maintain an Ansible playbook for specifically this if that helps. I tried to compile Chromium for Node 10 runtime and failed, so if you want to have a shot at this let me know how I can help.
@alixaxel,
@olecom What do you mean by infrastructure?
After digging into build errors: https://circleci.com/gh/adieuadieu/serverless-chrome/3676
it is evident that there are no new docker images to build new versions of serverless chrome binary: https://hub.docker.com/r/adieuadieu/headless-chromium-for-aws-lambda/tags
To provide such images there should be some local or EC2 machines: https://github.com/adieuadieu/serverless-chrome/blob/master/docs/chrome.md
This is why I thought that there is no more infrastructure for build process...
Is this still an issue?