Built-in container support for the .NET SDK

Hey folks - author here, happy to answer any questions about the feature or what we&#x27;re hoping to do with it.<p>Broadly we just want to lower barriers to containerization for all .NET developers. Jib&#x2F;Ko&#x2F;etc are proven patterns in this field, and we saw an opportunity to use the existing infrastructure of MSBuild to reduce the amount of concepts our users would need to know in order to be successful in their journey to the cloud. On top of that, having the feature in SDK provides some opportunities to help users adhere to conventions around container labeling (or customize container metadata entirely!) so we can make .NET containers good citizens in the container ecosystem overall.

What problem is this solving? I have been building containerized .NET applications for a couple of years now. It is super easy to use docker command to build x86 Linux and ARM docker images. I don&#x27;t think I&#x27;ll switch to Microsoft&#x27;s half-assed solution since the docker command works just fine.<p>Here&#x27;s the problem Microsoft should be solving instead: Once a docker image is built, how can my <i>customer</i> (not me) deploy it to Azure using their Azure account? I would like to provide a &quot;Deploy to Azure&quot; button similar to Heroku&#x27;s &quot;Deploy to Heroku&quot;. My customer should be able to deploy a web application using my docker image with <i>a single click</i>, using their Azure subscription. Heroku even provisions a Postgres database in the process. And it was all free until a couple of days ago.