Switch s390x and PPC64 to Mariner host OS, not ancient Ubuntu

[directhex]

No description provided.

[dotnet-policy-service]

Tagging subscribers to this area: @hoyosjs
See info in area-owners.md if you want to be subscribed.

[directhex]

/azp run runtime-community

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[am11]

Should we move new ones directly to azurelinux-3.0 (CBL-mariner rebranded)?

[directhex]

I'm not opposed, but that'll take longer (we already had these Mariner 2 images lying around unused for the past X months, it'd take a little while to get new 3 images built)

[am11]

Sounds good. BTW, I found it a bit strange/unnecessary that azurelinux tags have -net8 suffix (rarely we add/remove dependencies and mostly we just add a new one).

[directhex]

Sounds good. BTW, I found it a bit strange/unnecessary that azurelinux tags have -net8 suffix (rarely we add/remove dependencies and mostly we just add a new one).

I admit that suffix was a large part of my "er, no idea what's going on here, I'll just stick with 2"

[akoeplinger]

Awesome!

[akoeplinger]

BTW, I found it a bit strange/unnecessary that azurelinux tags have -net8 suffix (rarely we add/remove dependencies and mostly we just add a new one).

We just hit this today with the wasm images where updating a dependency would break existing image usages so in general I prefer being explicit.

[akoeplinger]

The s390x failures are known: #101380 (comment)

[akoeplinger]

/ba-g the runtime-community pipeline passed which is all that counts

[am11]

We just hit this today with the wasm images where updating a dependency would break existing image usages so in general I prefer being explicit.

That is not a new problem. We've been using docker tags (pinned vs. floating) to solve it when needed. New convention of hardcoding .NET version in the tag is going to produce much noise and it's wasteful when there is no 1:1 relationship.