Known issues for containers
There are a few issues when installing Visual Studio into a Docker container.
The following known issues occur when you install Visual Studio Build Tools 2017 into a Windows container.
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 Windows SDK version 10.0.14393 or earlier. Certain packages fail to install and workloads that depend on those packages will not work.
-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.
--norestarton the command line. As of this writing, attempting to restart a Windows container from within the container returns
ERROR_TOO_MANY_OPEN_FILESto the host.
If you base your image directly on microsoft/windowsservercore, the .NET Framework may not install properly and no install error is indicated. Managed code may not run after the install is complete. Instead, base your image on microsoft/dotnet-framework:4.7.1 or later. As an example, you may see an error when building with MSBuild like:
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=22.214.171.124, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
You cannot install Visual Studio 2017 version 15.8 or earlier (any product) on mcr.microsoft.com/windows/servercore:1809 or later. See https://aka.ms/setup/containers/servercore1809 for more information.
Build Tools container
The following known issues might occur when you use a Build Tools container. To see whether issues have been fixed or if there are other known issues, visit https://developercommunity.visualstudio.com.
- IntelliTrace may not work in some scenarios within a container.
Sometimes, things can go wrong. If your Visual Studio installation fails, see Troubleshooting Visual Studio 2017 installation and upgrade issues for step-by-step guidance.
We also offer a live chat (English only) support option for installation-related issues.
Here are a few more support options:
- Report product issues to us via the Report a Problem tool that appears both in the Visual Studio Installer and in the Visual Studio IDE.
- Suggest a feature, track product issues, and find answers in the Visual Studio Developer Community.
- Use your GitHub account to talk to us and other Visual Studio developers in the Visual Studio conversation in the Gitter community.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.