[Lambda] Support pulling container images via OCI index platform-specific digest lookup
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- aws, docker
- Domain
- cloud
Research direction
The issue names AWS Lambda, AWS ECR, Docker buildx, and OCI indexes but provides no repository files, tests, or entry points. Start by reviewing the Lambda container-image and OCI index behavior described in the issue; done means Lambda can pull the platform-specific digest from the index without disabling provenance.
Written by the indexing model from the issue text.
Description
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
Support pulling container images via OCI index platform-specific digest lookup.
Which service(s) is this request for?
AWS Lambda
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Recent versions of Docker buildx default to enabling provenance which causes an OCI index to be created with the specified image tag pointing to untagged image(s).
However, AWS Lambda does not support pulling the image by looking up the image via its platform-specific digest in that OCI index.
Error message:
The image manifest, config or layer media type for the source image <image_name> is not supported. (Service: Lambda, Status Code: 400, Request ID: <request_id>) (SDK Attempt Count: 1)"
Are you currently working around this issue?
By disabling provenance during image builds.
Additional context
Registry is AWS ECR.
Attachments
None.
- Dominant language
- No language data
- Stars
- 196
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aws/aws-lambda-roadmap
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
aws/aws-lambda-roadmap#101 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
aws/aws-lambda-roadmap#100 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 28/100
aws/aws-lambda-roadmap#97 · 1 comment · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
aws/aws-lambda-roadmap#96 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
aws/aws-lambda-roadmap#95 · 1 comment · 1 reaction ·
All issues in aws/aws-lambda-roadmap
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
carverauto/serviceradar#4596 ·
-
complexity: small feature: security role: DevOps Engineer size: 2pt
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
hackforla/devops-security#203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
OpenHands/OpenHands-Cloud#1283 ·
-
[BUG] ECR GetAuthorizationToken returns a proxyEndpoint for the default region, not the request's Openbug ecr
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
docs-from-code
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoft/aspire.dev#1734 ·