Re-enable system-data-odbc test on alpine:edge

[omajid]

We are disabling it in #222 but we should re-enable it when the underlying issues are fixed on Alpine.

[soutieslak]

Hi @omajid, I have been following a number of threads on this whole "dotnet RID being selected on Alpine causing issues" topic. II finally came across this test case that has been disabled and was wondering if there is any status update on it?

[omajid]

Hey, @soutieslak .

.NET has a couple of long standing issues in how it handles RIDs. The fundamental fixes are still being discussed. However, most of these bugs have workarounds in place that should prevent users from hitting them.

For Alpine specifically, an issue still exists when it comes to handling the in-development versions of alpine. Released versions (eg, 3.17, 3.16) should be fine. The specific bug is tracked by dotnet/runtime#73525

Does that help? Do you have a specific bug that you are running into?

[soutieslak]

Thanks for the reply @omajid!

I am using the official ASP.NET Core runtime image as my base image i.e. "mcr.microsoft.com/dotnet/aspnet:7.0.2-alpine3.17-amd64".

When I want to populate my image with my application, I follow these 4 basic steps:
dotnet restore
dotnet build
dotnet publish
copy the published app to the container

So in other words, I am publishing my application for all RIDs, but then when I run my container, I get a segmentation fault -> This is where I assumed its selecting the wrong RID.

I then tried a different approach, and instead of publishing my application for all RIDs, I targeted a specific RID i.e. 'linux-musl-x64'. This results in a single RID variant of my application. If I then copy this published app to the container, it works as expected.

This is why I still think this is a bug. But now I am confused on who's side, Alpine (specifically 3.16 and 3.17) or dotnet. I get the same result with .Net6.0 and .Net7.0

Edit: I'm going to post my scenario from above on dotnet/runtime#73525

[omajid]

That sounds an entirely different bug to me. Reporting it to the dotnet project is a good idea. If can post the complete steps to demonstrate this with a hello-world-style project, that would be even better.