Errors with sentry-native launching with Sentry.AspNetCore on Dockerized Native AOT builds on Linux

[ionite34]

Package

Sentry

.NET Flavor

.NET

.NET Version

9.0.201

OS

Linux

OS Version

alpine 3.21

Development Environment

Other

SDK Version

5.5.1

Self-Hosted Sentry Version

No response

Workload Versions

N/A

UseSentry or SentrySdk.Init call

N/A

Steps to Reproduce

1. Using any minimal api AOT example, such as:

var builder = WebApplication.CreateSlimBuilder(args);

builder.Services.AddSentry();

var app = builder.Build();

api.MapGet("test", () => "Test Ok");

await app.RunAsync();

2. Building with this Dockerfile:

FROM mcr.microsoft.com/dotnet/nightly/sdk:9.0.201-alpine3.21-aot AS build
WORKDIR /src

COPY --link . .
RUN dotnet publish -c Release -a linux-musl-x64 -o /app ./Project/Project.csproj
RUN rm /app/*.dbg /app/*.Development.json

FROM mcr.microsoft.com/dotnet/nightly/runtime-deps:9.0.3-alpine3.21-aot AS final
USER $APP_UID
EXPOSE 8080
EXPOSE 8081
ENV ASPNETCORE_URLS=http://+:8080

WORKDIR /app
COPY --link --from=build /app .
ENTRYPOINT ["./Project"]

Expected Result

Should be able to launch normally

Actual Result

Upon hitting endpoints we'll get a 500 error with:

Unhandled exception. System.DllNotFoundException: Unable to load shared library 'sentry-native' or one of its dependencies. In order to help diagnose loading problems, consider using a tool like strace. If you're using glibc, consider setting the LD_DEBUG environment variable: 

Error loading shared library sentry-native.so: No such file or directory
Error loading shared library libsentry-native.so: No such file or directory
Error loading shared library sentry-native: No such file or directory
Error loading shared library libsentry-native: No such file or directory

   at System.Runtime.InteropServices.NativeLibrary.LoadLibErrorTracker.Throw(String) + 0x46
   at Internal.Runtime.CompilerHelpers.InteropHelpers.FixupModuleCell(InteropHelpers.ModuleFixupCell*) + 0x139
   at Internal.Runtime.CompilerHelpers.InteropHelpers.ResolvePInvokeSlow(InteropHelpers.MethodFixupCell*) + 0x35
   at Sentry.Native.C.sentry_options_new() + 0x1f
   at Sentry.Native.C.Init(SentryOptions) + 0x1f
   at Sentry.SentrySdk.InitNativeSdk(SentryOptions) + 0x2d
   at Sentry.SentrySdk.InitHub(SentryOptions) + 0x185
   at Sentry.SentrySdk.Init(Action`1) + 0x3a
   at Program.<<Main>$>d__0.MoveNext() + 0xde

Might be related to #4116 and #4102

An option to disable this sentry-native usage might be helpful for now since this is a blocker for us deploying Sentry at all on our Native AOT containers just for request exceptions logging and traces.

We're currently using https://www.nuget.org/packages/Microsoft.ApplicationInsights.aspnetcore on these containers, and despite build time trim warnings it still works fine so far in regards to capturing exceptions and traces.

[bruno-garcia]

Thanks for raising this.

to unblock you, there is an option in MSbuild you can use DisableSentryNative if u set to false stops sentry from adding it.

We might rename that to SentryDisableNative but we'll keep it backward compatible at least until version 6.0 of the sdk.

Looks like this option was released yet so we'll put a release out asap to unblock you.

• Add DisableSentryNative build property #4107

Other than that we need to debug this as this shouldn't be happening.

Are you using a proper nuget dependency? like adding sentry via nuget? is something possibly deleting our native libraries from the obj/bin folders?

[bruno-garcia]

We'll ship a release tomorrow either with the option name. Or with the current solution so you can work around this.

But looking in more detail about the issue: /runtime-deps:9.0.3-alpine3.21-aot perhaps we don't have sentry-native in a way that's compatible with this? Is it a musl Linux situation? @vaind might have thoughts

Note the publish args: linux-musl-x64
We bundle these sentry-native static libs:

linux-x64 is there, should that work on musl linux?
Does .NET look at linux-x64 when resolving the directoy? Or does it look at linux-musl-x64 and hence we need to build a new version and add to a new directory? @filipnavara might know this one.

[filipnavara]

Does .NET look at linux-x64 when resolving the directoy? Or does it look at linux-musl-x64 and hence we need to build a new version and add to a new directory?

I think you might need to build a new one. Even if it looked for the directory (which can be checked with the RID graph) the native binaries are generally not portable between different libc implementations.

[vaind]

We specify the path explicitly, so after adding the build, we'll also need to update this code:

sentry-dotnet/src/Sentry/Platforms/Native/buildTransitive/Sentry.Native.targets

Lines 36 to 41 in 084e3b4

	<ItemGroup Condition="'$(FrameworkSupportsNative)' == 'true' and '$(RuntimeIdentifier)' == 'linux-x64'">
	<DirectPInvoke Include="sentry-native" />
	<NativeLibrary Include="$(MSBuildThisFileDirectory)..\sentry-native\linux-x64\libsentry-native.a" />
	<!-- See: https://github.com/dotnet/runtime/issues/97414 -->
	<NativeSystemLibrary Include="curl" />
	</ItemGroup>