Merge pull request #8282 from msangapu-msft/patch-2

Docker to MCR

Author: PRMerger16

docs/install/build-tools-container-issues.md

@@ -23,7 +23,7 @@ The following known issues occur when you install Visual Studio Build Tools into
 
 ::: moniker range="vs-2017"
 
-* You cannot install Visual Studio into a container based on image microsoft/windowsservercore:10.0.14393.1593. Images tagged with Windows versions before or after 10.0.14393 should work.
+* You cannot install Visual Studio into a container based on image mcr.microsoft.com/windows/servercore:10.0.14393.1593 . Images tagged with Windows versions before or after 10.0.14393 should work.
 
 * You cannot install Windows SDK version 10.0.14393 or earlier. Certain packages fail to install and workloads that depend on those packages will not work.
 
@@ -32,7 +32,7 @@ The following known issues occur when you install Visual Studio Build Tools into
 * Pass `-m 2GB` (or more) when building the image. Some workloads require more memory than the default 1 GB when installed.
 * Configure Docker to use disks larger than the default 20 GB.
 * Pass `--norestart` on the command line. As of this writing, attempting to restart a Windows container from within the container returns `ERROR_TOO_MANY_OPEN_FILES` to the host.
-* If you base your image directly on microsoft/windowsservercore, the .NET Framework might not install properly and no install error is indicated. Managed code might not run after the install is complete. Instead, base your image on [microsoft/dotnet-framework:4.7.1](https://hub.docker.com/r/microsoft/dotnet-framework) or later. As an example, you might see an error when building with MSBuild that's similar to the following:
+* If you base your image directly on mcr.microsoft.com/windows/servercore, the .NET Framework might not install properly and no install error is indicated. Managed code might not run after the install is complete. Instead, base your image on [microsoft/dotnet-framework:4.7.1](https://hub.docker.com/r/microsoft/dotnet-framework) or later. As an example, you might see an error when building with MSBuild that's similar to the following:
 
   > C:\BuildTools\MSBuild\15.0\bin\Roslyn\Microsoft.CSharp.Core.targets(84,5): error MSB6003: The specified task executable "csc.exe" could not be run. Could not load file or assembly 'System.IO.FileSystem, Version=4.0.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.