Migrate off of EOL container images

[mthalman]

The following container images are unsupported to the distro being EOL and should be updated to supported versions:

wcf/eng/SendToHelix.proj

Line 34 in ed1bd7a

<HelixTargetQueue Include="(Debian.11.Amd64)[email protected]/dotnet-buildtools/prereqs:debian-11-helix-amd64" />

wcf/eng/SendToHelix.proj

Line 40 in ed1bd7a

<HelixTargetQueue Include="(Fedora.38.Amd64.Open)[email protected]/dotnet-buildtools/prereqs:fedora-38-helix" />

wcf/eng/SendToHelix.proj

Line 42 in ed1bd7a

<HelixTargetQueue Include="(Debian.11.Amd64.Open)[email protected]/dotnet-buildtools/prereqs:debian-11-helix-amd64" />

wcf/eng/SendToHelix.proj

Line 44 in ed1bd7a

<HelixTargetQueue Include="(openSUSE.15.2.Amd64.Open)[email protected]/dotnet-buildtools/prereqs:opensuse-15.2-helix-amd64" />

Related:
Debian 11: dotnet/core#9625
Fedora 38: dotnet/core#9291

[mconnew]

@mthalman, can you provide us with a versionless docker container names/tags that just represents the latest of the distro so that we don't need to maintain these?

[mthalman]

@mthalman, can you provide us with a versionless docker container names/tags that just represents the latest of the distro so that we don't need to maintain these?

There are no such tags and we explicitly do not want them to avoid the potential for breaking the build. Coincidentally, this is specifically called out at https://github.com/dotnet/dotnet-buildtools-prereqs-docker/pull/1274/files#diff-59c2cf35a49a17d78cfac4d681eca2c123f5c0ea49579b99b284916b1628f395R52.

[mconnew]

Our build has never been broken due to moving distro versions. We have had multiple build breakages due to expiring OS versions (it was Helix queues for specific distribution versions were retired without notification, but it'sthe same underlying issue, the need to keep updating the send to helix config). For this repo at least, we would have better build stability if there was a latest tag than we've had with the distro product version being locked down.

[mthalman]

I would suggest logging an issue at https://github.com/dotnet/dotnet-buildtools-prereqs-docker/issues to make your case on why this would be useful.

[mthalman]

For reference purposes, here's the follow-up issue that was created: dotnet/dotnet-buildtools-prereqs-docker#1279