New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Windows Server 2019 #189

Open
sixeyed opened this Issue Oct 4, 2018 · 7 comments

Comments

Projects
None yet
3 participants
@sixeyed

sixeyed commented Oct 4, 2018

The Windows Server Core Docker image is GA now at mcr.microsoft.com/windows/servercore:1809. It already has .NET 4.7 installed, but an sdk image would be great to have (we already have them for .NET Core via PR 719).

@MichaelSimons

This comment has been minimized.

Show comment
Hide comment
@MichaelSimons

MichaelSimons Oct 10, 2018

Member

Note the base OS images are currently not available. See https://support.microsoft.com/en-us/help/4464619/windows-10-update-history.

Member

MichaelSimons commented Oct 10, 2018

Note the base OS images are currently not available. See https://support.microsoft.com/en-us/help/4464619/windows-10-update-history.

@davidmatson

This comment has been minimized.

Show comment
Hide comment
@davidmatson

davidmatson Oct 16, 2018

@MichaelSimons - can you clarify regarding base OS image availability? I believe mcr.microsoft.com/windows/servercore:1809 has been available for a couple of weeks now, separate from the Windows 10 rollout.

davidmatson commented Oct 16, 2018

@MichaelSimons - can you clarify regarding base OS image availability? I believe mcr.microsoft.com/windows/servercore:1809 has been available for a couple of weeks now, separate from the Windows 10 rollout.

@davidmatson

This comment has been minimized.

Show comment
Hide comment
@davidmatson

davidmatson Oct 16, 2018

Or I guess that image got removed after it had initially been made available? I have it locally but docker pull mcr.microsoft.com/windows/servercore:1809 is now failing with a not found error.

davidmatson commented Oct 16, 2018

Or I guess that image got removed after it had initially been made available? I have it locally but docker pull mcr.microsoft.com/windows/servercore:1809 is now failing with a not found error.

@MichaelSimons

This comment has been minimized.

Show comment
Hide comment
@MichaelSimons

MichaelSimons Oct 16, 2018

Member

The base OS images were pulled and are no longer available.

Member

MichaelSimons commented Oct 16, 2018

The base OS images were pulled and are no longer available.

@sixeyed

This comment has been minimized.

Show comment
Hide comment
@sixeyed

sixeyed Oct 22, 2018

@MichaelSimons can I ask if you got a working version of the 4.7.2 SDK on 1809 using the Dockerfiles in the rs5 branch? I've tried building using a cached local copy of the base image, but the VS Build Tools don't install. I get a bunch of NGen errors, but after removing those calls VS installs without errors but there's no VS 2017 folder in Program Files (x86). Also tried with Chocolatey and I get the same result - no errors, but no VS 2017. Wondering if there's a missing Windows feature I need to enable?

sixeyed commented Oct 22, 2018

@MichaelSimons can I ask if you got a working version of the 4.7.2 SDK on 1809 using the Dockerfiles in the rs5 branch? I've tried building using a cached local copy of the base image, but the VS Build Tools don't install. I get a bunch of NGen errors, but after removing those calls VS installs without errors but there's no VS 2017 folder in Program Files (x86). Also tried with Chocolatey and I get the same result - no errors, but no VS 2017. Wondering if there's a missing Windows feature I need to enable?

@MichaelSimons

This comment has been minimized.

Show comment
Hide comment
@MichaelSimons

MichaelSimons Oct 22, 2018

Member

@sixeyed - There is a compatibility issue between the1809 OS images and the VS Installer. The product teams are aware of the issue and a fix is forthcoming.

Member

MichaelSimons commented Oct 22, 2018

@sixeyed - There is a compatibility issue between the1809 OS images and the VS Installer. The product teams are aware of the issue and a fix is forthcoming.

@sixeyed

This comment has been minimized.

Show comment
Hide comment
@sixeyed

sixeyed Oct 23, 2018

Thanks for the update @MichaelSimons - I'll stop trying for now :)

sixeyed commented Oct 23, 2018

Thanks for the update @MichaelSimons - I'll stop trying for now :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment