[Migrated] Add Docker Container Image Support

[jneves]

Originally from: Miserlou/Zappa#2188 by ian-whitestone

Earlier this month, AWS announced container image support for AWS Lambda. This means you can now package and deploy lambda functions as container images, instead of using zip files. The container image based approach will solve a lot of headaches caused by the zip file approach, particularly with file sizes (container images can be up to 10GB) and the dependency issues we all know & love.

In an ideal end state, you should be able to call zappa deploy / zappa update / zappa package (etc.) and specify whether you want to use the traditional zip-based approach or new Docker container based approach. If choosing the latter, Zappa would automatically:

• Build the new docker image for you
  • Not 100% sure how this would work yet. There is a Python library for docker that could be used. Would need to detect the dependencies a user has in their virtual env. and then install them all in the Docker image creation flow.
  • A simpler alternative could involve a user having a Dockerfile that they point Zappa to, and Zappa just executes the build for that.
• Pushes the docker image to Amazon's Container Registry solution
  • Automatically creates new repository if one does not exist
• Creates the lambda function with the new Docker image

For a MVP, we should take a BYOI (bring your own image) approach and just get zappa deploy and zappa update to deploy a lambda function using an existing Docker Image that complies with these guidelines.

[HsnVahedi]

Hi, Why did you close this issue? Is there any plans to support container images in the future?

[sean-mcclure]

Zappa seriously needs this. Most practical applications exceed the zip file size limit.