Document BYO ECR images as the MicroVM container base - #6
Merged
Conversation
Partners already publish application images from CI/CD. Lambda still builds from a Dockerfile zip plus a managed MicroVM OS; their ECR image is FROM in that Dockerfile, with this repo's worker runtime layered on top. Grant the build role private ECR pull so that path works. Co-authored-by: Jack Pertschuk <jp954@cornell.edu>
pertschuk
marked this pull request as ready for review
August 28, 2026 13:23
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Partners who already publish an application image to ECR from CI/CD can use that image as the MicroVM container base. Lambda still does not take an ECR URI as the MicroVM image itself.
How it works
create-microvm-imagestill takes--code-artifact(zip with aDockerfile+ Cursor worker files) and--base-image-arn(a Lambda-managed MicroVM OS fromlist-managed-microvm-images).FROMin that Dockerfile. This repo’s worker runtime (CLI, git,hook.py/ready/validate/run,entrypoint.sh) is layered on top./readyand/validatestay enabled oncreate-microvm-image/--hooks, same as the stock path.This PR
microvm-image/Dockerfile.ecras a thin example that stays in sync with the stock Dockerfile’s CLI install / COPY / ENTRYPOINT. The stock Dockerfile remains the quickstart.BuildRolewith private ECR pull:ecr:GetAuthorizationToken(Resource: *, required for that action) and layer pull scoped to this account’s repositories.Out of scope: no change to the default image path, no lab CLI pin docs, not merged.
Docs: https://docs.aws.amazon.com/lambda/latest/dg/microvms-images.html