Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
FROM public.ecr.aws/lambda/python:3.6
FROM python:3.13-alpine
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you clarify the motivation for this change?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes sure. The context is:

  • Back in the day, Lambda image behaviour was like executing a job: run and exit
  • Now, all Lambda image act like a backend server: keep running forever

When I tried the old Dockerfile, StateMachine execution never escape RUNNING state as ECS serve the image as a server.

So I decided to use the plain python image.

One weird thing is although there is a test using the changed Dockerfile, no snapshot change was detected. So I only ran my new test file.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One weird thing is although there is a test using the changed Dockerfile, no snapshot change was detected. So I only ran my new test file.

After checking the implementation of DockerImageAsset I don't see any logic which use the docker file's content to compute asset's hash.

EXPOSE 8000
WORKDIR /src
ADD . /src
CMD python3 index.py
CMD python index.py
Loading