Skip to content
This repository has been archived by the owner on Jan 23, 2023. It is now read-only.
/ corefx Public archive

Adding Alpine 3.8 and 3.9 to the RID graph #34789

Merged
merged 2 commits into from
Feb 13, 2019

Conversation

joperezr
Copy link
Member

@joperezr joperezr commented Jan 23, 2019

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

Copy link
Member

@eerhardt eerhardt left a 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

Copy link
Member

@MichaelSimons MichaelSimons left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@joperezr
Copy link
Member Author

test failures are not related to my PR.

@danmoseley danmoseley added the Servicing-consider Issue for next servicing release review label Jan 29, 2019
@stephentoub
Copy link
Member

@dotnet-bot test this please

@jamshedd jamshedd added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Jan 29, 2019
@jamshedd
Copy link
Member

Approved for 2.2.3.

@danmoseley
Copy link
Member

@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?

@eerhardt
Copy link
Member

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?

See https://github.com/dotnet/corefx/issues/34316#issuecomment-451485481 for 2 approaches that will fix this better in the future.

@jamshedd jamshedd added this to the 2.2.3 milestone Jan 29, 2019
@danmoseley
Copy link
Member

Branch not quite open yet

@danmoseley danmoseley added the * NO MERGE * The PR is not ready for merge yet (see discussion for detailed reasons) label Jan 29, 2019
@wtgodbe wtgodbe removed the * NO MERGE * The PR is not ready for merge yet (see discussion for detailed reasons) label Feb 13, 2019
@wtgodbe wtgodbe merged commit 615560d into dotnet:release/2.1 Feb 13, 2019
@karelz
Copy link
Member

karelz commented Mar 18, 2019

@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).

@karelz karelz modified the milestones: 2.2.3, 2.1.9 Mar 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Servicing-approved Approved for servicing release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants