-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add .NET runtimes #13
Comments
It's especially confusing that such a container is listed on the ECR Public Gallery, but has no data/tags associated with it.
Even more than consistency, this lack prevents certain optimizations for .NET Lambda Functions. Deploying an application as |
Will this issue also cover introducing an AWS SAM build image for |
I do not intend to, at least. |
Yea of course @chrisoverzero. I was thinking perhaps an AW SAM build image for |
Image for .NET Core 3.1 merged. Closing this issue. |
* Adding dotnet7 image * Update to runtime image base * Add .NET 7 to attribution * Add dummy net7 test, add net7 to makefile * Use x86 specifically since dotnet7 is single arch * add dotnet7 build job Co-authored-by: Mehmet Nuri Deveci <[email protected]>
* Adding dotnet7 image * Update to runtime image base * Add .NET 7 to attribution * Add dummy net7 test, add net7 to makefile * Use x86 specifically since dotnet7 is single arch * add dotnet7 build job Co-authored-by: Mehmet Nuri Deveci <[email protected]> Co-authored-by: Beau Gosse <[email protected]>
Description
Currently there are not provided docker images for the .NET runtime, and the sam build command does not support the
--use-container
flag. This makes typical build and deploy workflows with SAM not working consistently for .NET projects. It would be great if a Docker image could be provided and the sam cli updated to work with the container.Benefits
Ensures consistent behavior for all AWS Lambda supported runtimes by the AWS SAM cli and build/deploy workflow.
Request
Add .NET Dockerfiles supporting AWS runtimes
The text was updated successfully, but these errors were encountered: