-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Provide Officially-Supported .NET AOT Images #5020
Comments
Hi @simonkurtz-MSFT, thanks for the feedback! If you are looking for a short-term, size efficient solution for publishing Native AOT apps, I'd encourage you to look at the releasesapi Debian sample. In that Dockerfile, you can replace the SDK tag with the Jammy SDK and the runtime deps tag with the Jammy Chiseled runtime deps image to get almost all of the size reduction benefits. We cover this in the .NET sample image size report. The only difference between the runtime-deps and the runtime-deps AOT image is the presence of the |
Any news on this topic? Both Keep up the great work! |
@zeroskyx we currently plan to provide some form of officially-supported Native AOT images for .NET 10. They may not be exactly the same as the AOT images that we currently have in nightly, but there will an easy way to build and host Native AOT apps without installing extra packages for most use-cases. We are still working out what that will look like. You can watch this issue for the latest info. |
We just published container optimizations to the Azure Container Apps .NET Workshop. This workshop provides guidance to our customers using ACA & .NET. Since ACA is Linux only, building for a specific platform with AOT is very suitable and would provide great advantages in terms of storage, transfer, start-up (no JIT compiler) and, likely, memory footpring.
Presently, the AOT images are nightly images, which doesn't instill much confidence with customers looking for a stable version. Please consider providing periodic AOT images given all the benefits they provide.
Thank you!
The text was updated successfully, but these errors were encountered: