Chrome flags required in an Amazon Lambda Docker image

I’m almost done making Phantomas run in an AWS Lambda Docker image. But I have an issue with Chrome not launching at all. I found a few answers thanks to this project: https://github.com/alixaxel/chrome-aws-lambda

It looks like Chrome requires to be started with the following additional flags: --no-sandbox --no-zygote --disable-gpu --single-process.

I think this use case won’t be shared with many other Phantomas users and I don’t want to complexify Phantomas with some hard to understand options such as --no-sandbox or --no-zygote. Any idea how we could do that? Would a single --aws-lambda-compatibility option be understandable/useful?

I still have the option to modify Phantomas’ code inside my Docker image.

[gmetais]

I’m wondering if we can automatically test phantomas in lambda somehow.

It is possible, but it’s kind of annoying. We first need to provide one of those:

• a zip file that includes the entire project, including dependencies compiled for Lambda machines
• a built docker image running on “Amazon Linux”

Then send it to AWS for deployment. And wait for deployment before testing.

[gmetais]

Otherwise yes, I can add a specific variable on my environment.