yeah I'm quite curious, but it appears to be undocumented outside of the code, it reads like a way to strip a container given a yaml config file to extract out the important bits.
We started with Red Hat. They were our .NET Core 1.0 launch partner (and remain a very close partner). You can run Red Hat on-prem or in the cloud (obviously).
We maintain container images for both Linux and Windows. I can tell you that they both get a LOT of use (>10M pulls/month). .NET is very much a cross-platform app stack. Also, we get plenty of bug reports on Linux (which we diligently fix). The days of .NET being Windows-only (and closed source) are long over.
Fedora and Red Hat have offered .NET packages for years. We've worked very closely with those folks and they've taught us a lot about how to work collaboratively with distro maintainers. We meet with them weekly. Notice that Fedora is mentioned in the blog post and here: https://docs.microsoft.com/dotnet/core/install/linux#officia....
This just puts Ubuntu at the same level as Fedora/RH/Arch were before, am I right? In the sense that this just means .Net is in the official repos (as was the case for Fedora/Arch before)
I've read that one. It's good, but not nearly as good as her other writing. I'm always torn by whether I like the earthsea or Hainish series better. She also has many wondering short stories, some of which borrow from her longer works.
I provided an answer in the blog post post comments. We see it most big corps and government. We also see Linux in those same places. If there are big Windows Server apps (typically .NET Framework) that people want to host in the cloud, then they often choose Windows Containers as the lowest friction solution, at least for step one. I work closely with the Windows Container team, and this is what I see from their customer engagements. Inside Microsoft, it is the same. Many big services at Microsoft have hard dependencies on Windows (both .NET Framework and Win32), and at the same time, many have also embraced Linux.
