Tweaks for SDK Container publish scenarios #6800
Conversation
| @@ -0,0 +1,12 @@ | |||
| # This image allows easily building and publishing AOT-compiled .NET applications | |||
There was a problem hiding this comment.
Having this image makes it fairly easy to create AOT'd ubuntu container variants using the .NET SDK - you map the Docker socket in and run the same publish command you would normally!
The one below is the same setup, but for Alpine Linux
| https://learn.microsoft.com/en-us/dotnet/core/containers/overview?tabs=windows --> | ||
| <EnableSdkContainerSupport>true</EnableSdkContainerSupport> | ||
| <RuntimeIdentifiers>linux-arm64;linux-x64</RuntimeIdentifiers> | ||
| <RuntimeIdentifiers Condition="'$(Alpine)' == 'true'">linux-musl-arm64;linux-musl-x64</RuntimeIdentifiers> |
There was a problem hiding this comment.
It's nice to be able to pivot to Alpine Linux easily - this sets the app up for simply showing multi-arch publishing as well.
There was a problem hiding this comment.
Is this Alpine property built-in?
There was a problem hiding this comment.
nope, I made it up (along with some of the other flags) just for scenario/convenience purposes. I think for real use cases users wouldn't need flags like this, they'd just decide what their deployment modality would be, but since the point is to make it easy to compare/contrast the same app in different modalities having simpler knobs helps.
There was a problem hiding this comment.
I think the documentation associated with this project should demonstrate this and other custom properties.
| <ImplicitUsings>enable</ImplicitUsings> | ||
| <Nullable>enable</Nullable> | ||
| <EnableSdkContainerSupport>true</EnableSdkContainerSupport> | ||
| <RuntimeIdentifiers>linux-arm64;linux-x64</RuntimeIdentifiers> |
There was a problem hiding this comment.
I've added a few 'pivots' to this project to show how a few relatively simple knobs can influence publishing. Broadly the pivots are
- platform: Nobel, Nobel-Chiseled, or Alpine
- Runtime: framework-dependent, self-contained, trimmed, or AOT
- Globalization: variant or invariant
choosing combinations of those knobs sets up the containerization to do different things. Most of the required changes were just to the ContainerFamily property for actual impact - this changes the base image used. The ContainerImageTag changes are just for us so we can more easily compare and contrast the changes - without changing the tag all of these publishes would use the latest tag by default.
Pivoting through the variants, you get something like the following (ordered by size):
>docker image list globalapp
REPOSITORY TAG IMAGE ID CREATED SIZE
globalapp alpine-aot-invariant a06647080c9a 7 minutes ago 24.3MB
globalapp alpine-aot-variant 2f60494c5b87 8 minutes ago 78.6MB
globalapp chiseled-aot-variant bfecdd20d2d1 11 minutes ago 81.8MB
globalapp chiseled-aot-invariant e12baf4a93b0 11 minutes ago 24.5MB
globalapp noble-variant fa56d4783f20 21 minutes ago 415MB
globalapp alpine e2bc432c4a16 21 minutes ago 183MB
globalapp alpine-trimmed-invariant bed2221d4a83 22 minutes ago 63.6MB
globalapp alpine-trimmed-variant e0fe24f9cfcf 23 minutes ago 133MB
globalapp alpine-sc-variant ac41be8d2f19 24 minutes ago 251MB
globalapp noble-trimmed-variant ac7cd08f90b4 29 minutes ago 296MB
globalapp noble-trimmed-invariant 05efcb0dd9cd 32 minutes ago 296MB
globalapp chiseled-trimmed-invariant 4bc0a3a87ae7 35 minutes ago 69.9MB
globalapp chiseled-trimmed-variant bdb06033a905 36 minutes ago 142MB
globalapp chiseled-sc-variant a6496ddf8bc8 37 minutes ago 422MB
globalapp chiseled-variant bdc0639ba482 37 minutes ago 261MB
globalapp chiseled 5a9503be26b2 44 minutes ago 189MB
globalapp latest 7587903084fb 47 minutes ago 415MB
| https://learn.microsoft.com/en-us/dotnet/core/containers/overview?tabs=windows --> | ||
| <EnableSdkContainerSupport>true</EnableSdkContainerSupport> | ||
| <RuntimeIdentifiers>linux-arm64;linux-x64</RuntimeIdentifiers> | ||
| <RuntimeIdentifiers Condition="'$(Alpine)' == 'true'">linux-musl-arm64;linux-musl-x64</RuntimeIdentifiers> |
There was a problem hiding this comment.
Is this Alpine property built-in?
| <!-- Learn more about .NET SDK container creation: | ||
| https://learn.microsoft.com/en-us/dotnet/core/containers/overview?tabs=windows --> | ||
| <EnableSdkContainerSupport>true</EnableSdkContainerSupport> | ||
| <RuntimeIdentifiers>linux-arm64;linux-x64</RuntimeIdentifiers> |
There was a problem hiding this comment.
We'd want this to work for Windows containers too.
There was a problem hiding this comment.
That's technically possible but out of the box Windows containers require extra work for the .NET SDK publishing - because the 'base images' no longer support Windows you have to specify your own ContainerBaseImage and related properties. Nothing I've done prevents that work in this project, it just doesn't make it super-simple.
Co-authored-by: Logan Bussell <[email protected]>
| # * call `dotnet publish -t PublishContainer` with/on a project that | ||
| # has been configured for AOT compilation | ||
| FROM --platform=$BUILDPLATFORM mcr.microsoft.com/dotnet/sdk:10.0-alpine-aot AS builder | ||
| RUN apk add --no-cache docker No newline at end of file |
There was a problem hiding this comment.
Since you're using the host's Docker socket you only need the docker-cli package:
| RUN apk add --no-cache docker | |
| RUN apk add --no-cache docker-cli |
There was a problem hiding this comment.
I tried to find an equivalent for Ubuntu but didn't see anything obvious.
3 participants
These are a few things I've changed to make SDK publishing scenarios 'pop' a bit more.