Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

.NET Framework Runtime and Builder Docker repos have merged #125

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

Closed
MichaelSimons opened this issue May 1, 2018 · 6 comments
Closed

.NET Framework Runtime and Builder Docker repos have merged #125

MichaelSimons opened this issue May 1, 2018 · 6 comments

Comments

@MichaelSimons
Copy link
Member

MichaelSimons commented May 1, 2018

.NET Framework Runtime and Builder Docker repos have merged

The microsoft/dotnet-framework-build Docker Hub repo has been merged into the microsoft/dotnet-framework Docker Hub repo. All new tags going forward will only be pushed to microsoft/dotnet-framework. The images in the microsoft/dotnet-framework-build Docker Hub repo will be retained and serviced accordingly as to not affect existing usage.

Details

The microsoft/dotnet-framework-build Docker Hub repo has been merged into the microsoft/dotnet-framework Docker Hub repo.

In order to differentiate the runtime and build images, runtime and sdk distinguishing identifiers have been added to the tags. For example, 4.7.2-runtime and 4.7.2-sdk.

All new tags going forward will only be pushed to microsoft/dotnet-framework. For example, the build images for 4.7.2 which was released today, only exist in microsoft/dotnet-framework repo.

The existing tags in microsoft/dotnet-framework-build will remain and be serviced accordingly. For example, the stable tags such as 4.7.1-windowsservercore-1709 will continue to be patched on a monthly basis.

We recommend that as you create and maintain your code, you move to use the new runtime and sdk images from the microsoft/dotnet-framework repo.

The microsoft/dotnet-framework-build Docker Hub repo will be deleted on 1/1/2019.

@robrich
Copy link

robrich commented May 5, 2018

Is this only for microsoft/dotnet docker images or will microsoft/aspnetcore images follow this new convention too?

@MichaelSimons
Copy link
Member Author

@robrich - this only applies to the microsoft/dotnet-framework images - i.e. the full .NET Framework. The microsoft/dotnet images already followed this convention. microsoft/aspnetcore is being transitioned in a different sorts in 2.1. See aspnet/aspnet-docker#403 for details.

@MichaelSimons
Copy link
Member Author

Closing issue but feel free to continue the conversation.

@tstrass
Copy link

tstrass commented Jun 29, 2018

What are the images tagged without -sdk or -runtime, e.g. dotnet-framework:4.7.1?

@MichaelSimons
Copy link
Member Author

They are equivalent to the -runtime images. We recommend moving off of these tags onto the -runtime tags. They are no longer being documented.

@rahulrai-in
Copy link

What is the recommendation for building .net Core SPA images? dotnet build restores the node and nuget packages and therefore requireds both npm and dotnet to be present in the image. aspnetcore-build had both the dependencies available.

@microsoft microsoft locked and limited conversation to collaborators Apr 13, 2022
@mthalman mthalman converted this issue into discussion #915 Apr 13, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
None yet
Development

No branches or pull requests

4 participants