Matt Thalman

> Obviously the fetch flow even in 2.x has access to some of this data (assuming what you are looking for is just image metadata from the manifest JSON) so...

If this repo has any other active branches that are used for servicing releases, those branches will need to have these changes ported over.

> @valentynbulakh - thanks for the details - please open issue - https://github.com/dotnet/dotnet-docker as mentioned earlier - the packages you are referring to are not direct dependencies for the images...

cc @MichaelSimons, @ashnaga

I see no mention of Windows containers in this thread so I'll throw that in as another use case. It would be great to have a Windows Dockerfile authoring experience...

There appears to be a new code path in 6.0.400 that now requires urlmon.dll in this scenario. That file does not exist in Windows Nano Server (it never has): ```console...

> The problem is that while `packagename*` works when the dependency is expressed in a deb, doing the same from a bash script or directly with the package manager does...

This issue is somewhat related to https://github.com/dotnet/coreclr/issues/26303. In an ideal world, we'd have one master list of native dependencies. Documentation could be updated programatically by reading from this master list.

Reopening because this is still relevant. There is a larger effort to better manage the descriptions of native dependencies at https://github.com/dotnet/core/issues/5651.

I'm experiencing the same thing. I'm pulling an image by digest, tagging it, and pushing it back. The digest from the push is different. Here are my logs illustrating the...