Install Build Tools into a container

You can install Visual Studio Build Tools into a Windows container to support continuous integration and continuous delivery (CI/CD) workflows. This article guides you through what Docker configuration changes are required as well as what workloads and components you can install in a container.

Containers are a great way to package a consistent build system you can use not only in a CI/CD server environment but for development environments as well. For example, you can mount your source code into a container to be built by a customized environment while you continue to use Visual Studio or other tools to write your code. If your CI/CD workflow uses the same container image, you can rest assured that your code builds consistently. You can use containers for runtime consistency as well, which is common for micro-services using multiple containers with an orchestration system; however, is beyond the scope of this article.

If Visual Studio Build Tools does not have what you require to build your source code, these same steps can be used for other Visual Studio products. Do note, however, that Windows containers do not support an interactive user interface so all commands must be automated.


Using Docker you create an image from which you can create containers that build your source code. The example Dockerfile installs the latest Visual Studio Build Tools 2017 and some other helpful programs often used for building source code. You can further modify your own Dockerfile to include other tools and scripts to run tests, publish build output, and more.

If you have already installed Docker for Windows, you can skip to step 3.

Step 1. Enable Hyper-V

Hyper-V is not enabled by default. It must be enabled to start Docker for Windows, since currently only Hyper-V isolation is supported for Windows 10.


Virtualization must be enabled on your machine. It is typically enabled by default; however, if Hyper-V install fails, refer to your system documentation for how to enable virtualization.

Step 2. Install Docker for Windows

If using Windows 10, you can download and install Docker Community Edition. If using Windows Server 2016, follow instructions to install Docker Enterprise Edition.

Step 3. Switch to Windows Containers

You can only install Build Tools 2017 on Windows, which requires you switch to Windows containers. Windows containers on Windows 10 support only Hyper-V isolation, while Windows containers on Windows Server 2016 support both Hyper-V and process isolation.

Step 4. Expand maximum container disk size

Visual Studio Build Tools - and to a greater extent, Visual Studio - require lots of disk space for all the tools that get installed. Even though the example Dockerfile disables the package cache, the disk size of container images must be increased to accommodate the space required. Currently on Windows, you can only increase disk size by changing the Docker configuration.

On Windows 10:

  1. Right-click on the Docker for Windows icon in the system tray and click Settings.

  2. Click on the Daemon section.

  3. Toggle the Basic button to Advanced.

  4. Add the following JSON array property to increase disk space to 120 GB (more than enough for Build Tools with room to grow).

      "storage-opts": [

    This property is added to anything you already have. For example, with these changes applied to the default daemon configuration file, you should now see:

      "registry-mirrors": [],
      "insecure-registries": [],
      "debug": true,
      "experimental": true,
      "storage-opts": [
  5. Click Apply.

On Windows Server 2016:

  1. Stop the "docker" service:

    sc.exe stop docker
  2. From an elevated command prompt, edit "%ProgramData%\Docker\config\daemon.json" (or whatever you specified to dockerd --config-file).

  3. Add the following JSON array property to increase disk space to 120 GB (more than enough for Build Tools with room to grow).

      "storage-opts": [

    This property is added to anything you already have.

  4. Save and close the file.

  5. Start the "docker" service:

    sc.exe start docker

Step 5. Create and build the Dockerfile

Save the following example Dockerfile to a new file on your disk. If the file is named simply "Dockerfile", it is recognized by default.


This example Dockerfile only excludes older Windows SDKs that cannot be installed into containers. Older releases cause the build command to fail.

  1. Open a command prompt.

  2. Create a new directory (recommended):

    mkdir C:\BuildTools
  3. Change directories to this new directory:

    cd C:\BuildTools
  4. Save the following content to C:\BuildTools\Dockerfile.

    # escape=`
    # Use the latest Windows Server Core image with .NET Framework 4.7.1.
    FROM microsoft/dotnet-framework:4.7.1
    # Restore the default Windows shell for correct batch processing below.
    SHELL ["cmd", "/S", "/C"]
    # Download the Build Tools bootstrapper.
    ADD C:\TEMP\vs_buildtools.exe
    # Install Build Tools excluding workloads and components with known issues.
    RUN C:\TEMP\vs_buildtools.exe --quiet --wait --norestart --nocache `
        --installPath C:\BuildTools `
        --all `
        --remove Microsoft.VisualStudio.Component.Windows10SDK.10240 `
        --remove Microsoft.VisualStudio.Component.Windows10SDK.10586 `
        --remove Microsoft.VisualStudio.Component.Windows10SDK.14393 `
        --remove Microsoft.VisualStudio.Component.Windows81SDK `
     || IF "%ERRORLEVEL%"=="3010" EXIT 0
    # Start developer command prompt with any other commands specified.
    ENTRYPOINT C:\BuildTools\Common7\Tools\VsDevCmd.bat &&
    # Default to PowerShell if no other command specified.
    CMD ["powershell.exe", "-NoLogo", "-ExecutionPolicy", "Bypass"]


    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 newer. Also note that newer images may use PowerShell as the default SHELL which will cause the RUN and ENTRYPOINT instructions to fail.

  5. Run the following command within that directory.

    docker build -t buildtools2017:latest -m 2GB .

    This command builds the Dockerfile in the current directory using 2 GB of memory. The default 1 GB is not sufficient when some workloads are installed; however, you may be able to build with only 1 GB of memory depending on your build requirements.

    The final image is tagged "buildtools2017:latest" so you can easily run it in a container as "buildtools2017" since the "latest" tag is the default if no tag is specified. If you want to use a specific version of Visual Studio Build Tools 2017 in a more advanced scenario, you might instead tag the container with a specific Visual Studio build number as well as "latest" so containers can use a specific version consistently.

Step 6. Using the built image

Now that you have created an image, you can run it in a container to do both interactive and automated builds. The example uses the Developer Command Prompt, so your PATH and other environment variables are already configured.

  1. Open a command prompt.

  2. Run the container to start a PowerShell environment with all developer environment variables set:

    docker run -it buildtools2017

To use this image for your CI/CD workflow, you can publish it to your own Azure Container Registry or other internal Docker registry so servers only need to pull it.

Get support

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:

See also