Is there an updated dockerfile for buildtools installations?

LE 0 Reputation points
2023-06-14T14:43:07.5533333+00:00

logs.txt

Description of the problem

I am using the dockerfile from (https://learn.microsoft.com/en-us/visualstudio/install/build-tools-container?view=vs-2022#create-and-build-the-dockerfile) but I changed the image FROM tag to “FROM mcr.microsoft.com/windows/servercore:ltsc2019”

The installation runs up to the point where the files are extracted and the setup launches. The setup immediately crashes with an error code.

I checked that the container is compatible with the vs buildtools v17 and it is . as per ( https://learn.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility?tabs=windows-server-2019%2Cwindows-11#windows-server-host-os-compatibility )

the log file is attached.
I tried to install windwos .net and it fails as well… not sure if this is required. as the orginal dockerfile doesn’t include it in the setup.

PS C:\installers> Install-WindowsFeature NET-Framework-Features Install-WindowsFeature : The request to add or remove features on the specified server failed. Installation of one or more roles, role services, or features failed. The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

is there a correct way to install the build tools in a dockerfile, as I can't see to get it to work reguardless of what image i use. Please advise if .net needs to be installed as the orginal dockerfile didn't include it.

ta,

Lane

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
4,098 questions
Visual Studio Setup
Visual Studio Setup
Visual Studio: A family of Microsoft suites of integrated development tools for building applications for Windows, the web and mobile devices.Setup: The procedures involved in preparing a software program or application to operate within a computer or mobile device.
1,194 questions
{count} votes

1 answer

Sort by: Most helpful
  1. LE 0 Reputation points
    2023-06-15T08:17:31.2166667+00:00

    As it turns out it was docker that was missing the proxy config for HTTPS connections....

    We are good! You can close the case. Thanks for the help!


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.