You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All other language run-times support the --use-container option for sam build except dotnet runtimes. With the addition of build images for dotnet it should now be possible to do this.
I've tested this with a quick hack here and it appears to work. I was able to successfully build and publish a dotnet6 runtime lambda via the following commands:
sam build -u
sam deploy --config-file samconfig.toml
However, I am guessing the change from read-only to read-write for the manifest dir is not ideal.
Proposal
Add support for dotnet lambda builds via docker containers to align with other runtime supported builds.
Things to consider:
May require updates to the docker build logic to support how it is handled via dotnet
The text was updated successfully, but these errors were encountered:
Hi @1davidmichael, wanted to give an update after discussing with the team: this is something that was on our map already, and we're in the process of prioritizing it, but we can't give any timelines at the moment.
Describe your idea/feature/enhancement
All other language run-times support the
--use-container
option forsam build
except dotnet runtimes. With the addition of build images for dotnet it should now be possible to do this.I've tested this with a quick hack here and it appears to work. I was able to successfully build and publish a
dotnet6
runtime lambda via the following commands:However, I am guessing the change from read-only to read-write for the manifest dir is not ideal.
Proposal
Add support for dotnet lambda builds via docker containers to align with other runtime supported builds.
Things to consider:
The text was updated successfully, but these errors were encountered: