Matt Thalman

One thing I think we should allow for is for multiple staged Dockerfiles for a given "base" image. We're in that situation today with https://github.com/dotnet/dotnet-buildtools-prereqs-docker/issues/1371 and https://github.com/dotnet/runtime/pull/112885#discussion_r1977837198. So I'd like...

[Triage] @siramvikram - There should be a primary issue for this logged in the dotnet/core repo. Can you take care of that please? @richlander - The issue https://github.com/dotnet/core/issues/9638 doesn't have...

> Instead of adding lots of complexity to our custom caching mechanism, maybe it's time to evaluate using [Docker's built-in caching](https://docs.docker.com/build/cache/backends/registry/). Maybe. But that defeats the whole purpose of https://github.com/dotnet/docker-tools/pull/1449....

Yeah, I think it's fine to remove it since it only applies to the buildtools repo.

It's just building Dockerfiles. You can repro by building this [Dockerfile](https://github.com/dotnet/dotnet-buildtools-prereqs-docker/blob/main/src/alpine/3.18/helix/amd64/Dockerfile), for example.

Nobody on our team is very knowledgeable on Python so we're just guessing here. But this is what might be the cause: https://github.com/dotnet/dotnet-buildtools-prereqs-docker/blob/a6ccb1abd3323eaa97bdb2a73c0a62c52c2225d6/src/alpine/3.18/helix/amd64/Dockerfile#L67 So if something recently rolled out there...

It also might be purely in the realm of a Python change, unrelated to Helix. We're not sure yet.

Fixed with https://github.com/dotnet/dotnet-buildtools-prereqs-docker/pull/1095

Chatted with @richlander offline. We agreed it will be acceptable to have a tags table represented. The support concerns have been addressed by https://github.com/dotnet/dotnet-buildtools-prereqs-docker/pull/1347.

> @sbomer - Friendly ping. Is this something you intend to complete? This PR is pretty old now. @sbomer - Any update here? Note that I've deleted all of the...