[CI] Enable Native AOT for Cli on linux-arm64, and linux-musl-x64

[radical]

• These are cross compiled on linux-x64 images.
  Co-authored by Alexander Köplinger [email protected]

• Add a check for the output of 'file' command on unix, to confirm that the native binary is for the correct arch. This is meant as a simply sanity check.

Contributes to #10288

[radical]

Internal build: https://dev.azure.com/dnceng/internal/_build/results?buildId=2757534&view=results

[Copilot]

Pull Request Overview

This PR enables Native AOT compilation for the Aspire CLI on linux-arm64 and linux-musl-x64 platforms by setting up cross-compilation infrastructure and adding binary validation checks.

• Configures cross-compilation containers and build environment for ARM64 and musl targets
• Adds linker arguments and file signature validation to ensure correct native binary generation
• Removes previous limitations that disabled Native AOT for these platforms

Reviewed Changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
src/Aspire.Cli/Aspire.Cli.csproj	Adds linker arguments for linux-musl-x64 cross-compilation
eng/pipelines/templates/build_sign_native.yml	Configures container selection for cross-compilation builds
eng/pipelines/azure-pipelines.yml	Defines cross-compilation containers with appropriate environments
eng/clipack/Common.projitems	Implements file signature validation for native binaries on Unix platforms
eng/clipack/Aspire.Cli.osx-x64.csproj	Adds file signature regex for macOS x64 binaries
eng/clipack/Aspire.Cli.osx-arm64.csproj	Adds file signature regex for macOS ARM64 binaries
eng/clipack/Aspire.Cli.linux-x64.csproj	Adds file signature regex for Linux x64 binaries
eng/clipack/Aspire.Cli.linux-musl-x64.csproj	Enables Native AOT and adds file signature regex for musl x64
eng/clipack/Aspire.Cli.linux-arm64.csproj	Enables Native AOT and adds file signature regex for ARM64

[radical]

/backport to release/9.4

[github-actions]

Started backporting to release/9.4: https://github.com/dotnet/aspire/actions/runs/16511371828

[eerhardt]

Why is this necessary? This doesn't seem right that we have to do this.

cc @agocke @MichalStrehovsky

[radical]

IIUC, this is fixed in net9.0 but Aspire.Cli targets net8.0 . cc @akoeplinger

[eerhardt]

We should find a time to update to net10.0. I started in #10167. Maybe when .NET 10 RC (or maybe preview7?) comes out, it would be a good time to switch to the latest. Advantages:

1. I noticed a decent disk size drop when I was trying it.
2. It would allow us to do "warnings as errors", which was also fixed in net9.0.
3. We could do RID-specific dotnet tool (dnx). So the AOT'd version would be in dotnet tool install

[joperezr]

Would that mean that we could no longer publish a dotnet tool that is installable in 8 or 9 SDKs though?

[joperezr]

( not saying that would be ab locker, just trying to understand the implications)

[eerhardt]

Would that mean that we could no longer publish a dotnet tool that is installable in 8 or 9 SDKs though?

Potentionally, yes.

[davidfowl]

I think thats is the case

cc @baronfel

[MichalStrehovsky]

Why is this necessary? This doesn't seem right that we have to do this.

FWIW this was fixed in dotnet/runtime#101213, looks like there's an LLVM bug asking why this is needed.

[baronfel]

Would that mean that we could no longer publish a dotnet tool that is installable in 8 or 9 SDKs though?

Yes, or at minimum you could publish a 8/9 to but it would need to be a different package id.

[akoeplinger]

@MichalStrehovsky FYI that's not really the issue here, the problem is that in 8.0 we only consider a cross build if the architecture doesn't match: https://github.com/dotnet/runtime/blob/43906bfc26e75a36b1e317211a085f2886862f1e/src/coreclr/nativeaot/BuildIntegration/Microsoft.NETCore.Native.Unix.targets#L35

But in this case we're cross-building from AzureLinux x64 -> Alpine Musl x64. Passing the linker flag directly works around that.