-
Notifications
You must be signed in to change notification settings - Fork 4.9k
Adding Alpine 3.8 and 3.9 to the RID graph #34789
Conversation
ed7881d
to
99d81d1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Thanks @joperezr
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
test failures are not related to my PR. |
@dotnet-bot test this please |
Approved for 2.2.3. |
@joperezr @MichaelSimons can we define a RID that covers all Alpine 3.x so we don't have to do this whenever they increment their minor versoin? Also, do we need a matching Nuget change, so that restore provides the correct assets? |
See https://github.com/dotnet/corefx/issues/34316#issuecomment-451485481 for 2 approaches that will fix this better in the future. |
Branch not quite open yet |
@jamshedd this is PR in 2.1 branch, not 2.2 -- fixing milestone to 2.1.9 (I assume that's where this fix got). |
Fixes: #34316
Description
Our Docker images have now moved to Alpine 3.8 and with .NET Core 2.1 and 2.2 we claim to support 3.7+. However, our RID graphs only have Alpine 3.7 on the graph, which means that whenever a customer has some special native assets for 3.8 they won't be selected correctly and customers may run into unexpected runtime issues. This change will add both Alpine 3.8 and 3.9 to the RID graph.
Customer Impact
If a customer uses one of our docker images, or is running Alpine 3.8, and want to use special native assets for the new version of the distro they will hit issues as their assets won't be correctly selected. There is a way to work around this for now by setting an environment variable (
DOTNET_RUNTIME_ID=linux-musl-x64
) but the proper fix is to add them to the RID graph.Regression?
No
Packaging reviewed?
No
Risk
Low. We have added RIDs many times in the past and it is rarely an issue.
cc: @eerhardt @MichaelSimons