Infer/Assign relevant RIDs for the user

[baronfel]

Right now, for the most efficient framework-dependent containers, a user has to enter a command like

dotnet publish -c Release --os linux --arch x64 -p:PublishProfile=DefaultContainer

manually specifying the OS and Arch (or, alternatively the entire RID via -r). In cases where we know something about the destination container (through inference?) is it possible to perform the build/publish cycle with a RID taken from that image's metadata?

Ideally, I'd like for the command dotnet publish -c Release -p:PublishProfile=DefaultContainer to have the same information as the command above.

[rainersigwald]

Is it possible to infer this? Aren't there Windows-based containers with the same multi-arch image name, for example mcr.microsoft.com/dotnet/runtime:6.0 is an alias for both Debian 6.0.8-bullseye-slim-amd64 and Windows Sever Core 6.0.8-windowsservercore-ltsc2022. I was hoping we could infer which of those was right from the RID 🙃

[baronfel]

That's a good point - RID should influence base image selection (and that's not something we're doing quite yet). It's very common for users to put these kinds of properties in a PublishProfile so that it's all wrapped up in a nice bow, so we could just lean into that.

Of course, that means that we'll likely need a doc section on customizing the publish profile for use in this way.

[baronfel]

We do this inference assumption now.