-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Closed
Labels
aws:lambdaAWS LambdaAWS Lambdaplatform: arm64/aarch64Issues related to Apple SiliconIssues related to Apple Siliconstatus: resolved/staleClosed due to stalenessClosed due to stalenessstatus: response requiredWaiting for a response from the reporterWaiting for a response from the reportertype: bugBug reportBug report
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
The Pro version of LocalStack supports fetching Lambda layers from AWS. Your lambda layer proxy probably uses the x86_64 architecture to extract the contents of a specified layer. Layers can, however, specify architectures they're compatible with and if a layer is only compatible with arm64, the proxy returns error 500.
Exception: Error code 500 when requesting layer content from proxy service
You can reproduce the issue by trying to fetch the arm64 version of my Git layer. arn:aws:lambda:eu-west-1:110966697890:layer:lambda-git-x86_64:1 works just fine, but arn:aws:lambda:eu-west-1:110966697890:layer:lambda-git-arm64:1 fails with the aforementioned error.
Expected Behavior
The layer should be downloaded successfully.
How are you starting LocalStack?
With a docker-compose file
Steps To Reproduce
How are you starting localstack (e.g., bin/localstack command, arguments, or docker-compose.yml)
Docker-Compose + SLS plugin
Environment
- OS: macOS Monterey
- LocalStack: 0.13.0 / latestAnything else?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
aws:lambdaAWS LambdaAWS Lambdaplatform: arm64/aarch64Issues related to Apple SiliconIssues related to Apple Siliconstatus: resolved/staleClosed due to stalenessClosed due to stalenessstatus: response requiredWaiting for a response from the reporterWaiting for a response from the reportertype: bugBug reportBug report