docker-lambda
docker-lambda copied to clipboard
lambci
feat: Add python3.9 runtime
Now that amazon added support for Python 3.9 it would be great to add Python 3.9 support https://aws.amazon.com/tw/about-aws/whats-new/2021/08/aws-lambda-adds-support-python-3-9/
This is an attempt to mimic: https://github.com/lambci/docker-lambda/commit/a94337ae2410a94a9ac878622eb82b26bc385a92#diff-0af1966588ced06e3143ae720245c9b7aeaae213c6921c12c742a166679cc505
But this has a dependency on the image being added to s3 see: https://github.com/lambci/lambci/issues/138
Just dropping by to let you know that I've created a fork of the project with Python 3.9 and ARM64 support. See my comment here for more details.
Hi @mhart, lambda added 3.9 in Aug this year -- would be great if you could review & merge this.
Can someone (@mhart ?) please approve and merge this PR? It's taking too long
Would be possible to add python3.10 so when AWS would add support for it in lambda, this container would be already available?
Looks like somebody already forked this project and solved it several months ago:
https://github.com/mLupine/docker-lambda
https://hub.docker.com/r/mlupin/docker-lambda
This repo hasn't been touched in a year now.
Since this repo seems to be dead for almost 2 years now, My colleague and I went searching for other solutions. One solution was to use the fork, created by mlupine, but because that's also a one-man-operation and the last update was 9 months ago, we searched further and guess what? We seem to have found a solution in AWS!! Recently AWS added support for Lambda Container Images and provides base images for Lambda. Look here: https://aws.amazon.com/blogs/aws/new-for-aws-lambda-container-image-support for all information and documentation.
Since this repo seems to be dead for almost 2 years now, My colleague and I went searching for other solutions. One solution was to use the fork, created by mlupine, but because that's also a one-man-operation and the last update was 9 months ago, we searched further and guess what? We seem to have found a solution in AWS!! Recently AWS added support for Lambda Container Images and provides base images for Lambda. Look here: https://aws.amazon.com/blogs/aws/new-for-aws-lambda-container-image-support for all information and documentation.
That's correct, and if you use serverless deployment, there is an ECR section under provider:
ecr:
images:
baseimage:
buildArgs:
cacheFrom:
path: "./"
file: "Dockerfile"
platform: linux/amd64 # see: https://github.com/aws/aws-lambda-base-images/issues/26
which will build and upload the docker image into ECR service for you. And the function handlers can reference the container image with a command path in a similar way as how it'd reference the code path previously.
*You'd need docker available on the deployment pipeline agent. **Also remember to set up a life-policy rule to tidy up images from previous deployments on ECR.
The serverless page for referencing-container-image-as-a-target has more details.
The advantage is that you can build and use one of AWS's images or customize your own and maintain them on ECR service. As a side-effect, you'd also overcome the 250Mb size limit that AWS Lambda has to offer (since the container route supports up to 10Gb). But I trust that there will be a longer cold-start using an image, so the container option may not be for everybody depending on the non-functional requirements.
@GordonSo pretty please with cherry sprinkles on top can we merge this PR in. This PR is blocking me from testing mocking a lambda on python 3.9 runtime with the moto framework
