Matt Thalman

The need for this is exemplified by https://github.com/dotnet/core/issues/8663. Depending on the outcome of https://github.com/dotnet/dotnet-docker/issues/4804, we should use `icu` as the example of what to install. If we end up producing...

The documentation should include notes on identifying that the desired package is defined as a slice and using it via chisel. And also handle a scenario where the desired package...

@tboby - We're following up on that at https://github.com/ubuntu-rocks/dotnet/issues/21#issuecomment-1791614707. Ultimately, we believe such documentation should be provided in a repo outside the context of just .NET as it is more...

Here's the link for how to configure the infrastructure to produce signed images: https://eng.ms/docs/more/containers-secure-supply-chain/signing (internal link).

[Triage] We should determine whether image signing will be done across all images (6.0, 7.0, 8.0) or on a version-by-version basis. Would we apply image signing to already released versions...

Related work item: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/2060356 (internal link)

I was able to revert all the changes which flowed `RegistryAuthContext` all over the place and replaced it with a DI solution: https://github.com/dotnet/docker-tools/pull/1262/commits/02e1e8c3ed34f200488474dade29bc90491862ad.

I'm going to hold off on merging this until https://github.com/dotnet/docker-tools/pull/1260 is merged and rolled out.

Source build has the same failure as https://github.com/dotnet/arcade/pull/14487.

@mmitche - I wanted to get your eyes on this. This is release infra stuff so not sure it belongs in this repo or who should take ownership.