-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
feat: Allow lambda image builder to use AL2023 #510
Comments
We are currently using https://docs.aws.amazon.com/lambda/latest/dg/runtimes-walkthrough.html |
Thanks for the advise. It is indeed quite straightforward to make my own bootstrap file for runtime.
The error message is a bit misleading because ref: https://github.com/aws/aws-lambda-base-images/blob/nodejs20.x/Dockerfile.nodejs20.x |
I'll be happy to take a PR for that.
IIRC it's just weird packaging but still AMZL2. You can confirm by checking |
Previously we required Amazon Linux 2023 (and the error message erroneously said Amazon Linux 2). With this change, we will still be using Amazon Linux 2023 by default, but Ubuntu and Amazon Linux 2 will also be supported. Note that this changes the default base image from `public.ecr.aws/lambda/nodejs:20-x86_64` to `public.ecr.aws/amazonlinux/amazonlinux:2023`. The new image contains all the packages in the old one plus a few more Python packages. The new image is a bit smaller so might load faster. The only difference should be nodejs 20 in `/var/lang` which also includes the Lambda runtime. Resolves #510 Resolves #423 BREAKING CHANGE: Node.js is no longer included by default with Lambda runner images
According to this announcement from AWS, it is now possible to use AL2023 for lambda base image. I think we should remove the warning saying
Lambda runner provider only supports Amazon Linux 2
.For time-being, people workaround this limitation by explicitly specify
baseDockerImage: 'public.ecr.aws/lambda/provided.al2023'
The text was updated successfully, but these errors were encountered: