-
Notifications
You must be signed in to change notification settings - Fork 1.9k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Breaking Change: .NET Docker Repo Name Change #2375
Labels
Comments
This was referenced Nov 10, 2020
Closed
kwokkan
added a commit
to kwokkan/card-hero
that referenced
this issue
Nov 14, 2020
kwokkan
added a commit
to kwokkan/card-hero
that referenced
this issue
Nov 14, 2020
* Update to use new Docker images for .NET 5. See: * dotnet/dotnet-docker#2375 * Reduce number of build jobs and consolidate them based on language. * Save npm cache at end so nuild cache can also be saved.
wangshuai-007
added a commit
to wangshuai-007/ReTag
that referenced
this issue
Nov 24, 2020
idavidmcdonald
added a commit
to alphagov/notifications-net-client
that referenced
this issue
Feb 15, 2021
We were using 2.1 of .NET core but this is not end of life. You can see on https://hub.docker.com/_/microsoft-dotnet-sdk that 3.1 is long term support. Also note, that the repo name has changed as per dotnet/dotnet-docker#2375. Also note, I could have upgraded us to 5.1 but I went for 3.1 for two reasons - it's a smaller change - good to know that we support the oldest .net stuff so we don't add anything in that is only supported by newer versions However, I could be easily persuaded to choose 5.1 instead.
4 tasks
This was referenced Feb 25, 2021
kodiakhq bot
pushed a commit
to Azure/iotedge
that referenced
this issue
Mar 10, 2021
- Linux AMD64: `3.1.12-alpine3.12` --> `3.1.13-alpine3.13` - Linux ARM32: `3.1.12-bionic-arm*` --> `3.1.13-bionic-arm*` (1.0.5.9-linux-arm*) - Address CR path different : dotnet/dotnet-docker#2375
darobs
pushed a commit
to darobs/iotedge
that referenced
this issue
Mar 22, 2021
- Linux AMD64: `3.1.12-alpine3.12` --> `3.1.13-alpine3.13` - Linux ARM32: `3.1.12-bionic-arm*` --> `3.1.13-bionic-arm*` (1.0.5.9-linux-arm*) - Address CR path different : dotnet/dotnet-docker#2375
mristin
added a commit
to eclipse-aaspe/server
that referenced
this issue
Mar 24, 2021
Microsoft updated the docker images due to the release of .NET 5. See dotnet/dotnet-docker#2375
mristin
added a commit
to eclipse-aaspe/server
that referenced
this issue
Mar 24, 2021
Microsoft updated the docker images due to the release of .NET 5. See dotnet/dotnet-docker#2375
mmYeung
added a commit
to mmYeung/dockers
that referenced
this issue
Sep 8, 2021
ronnelsantiago
added a commit
to ronnelsantiago/AspNetCore.Docs
that referenced
this issue
Feb 4, 2022
Update the docker pull path based on the new .net docker repo change. dotnet/dotnet-docker#2375
serpent5
pushed a commit
to dotnet/AspNetCore.Docs
that referenced
this issue
Feb 4, 2022
Update the docker pull path based on the new .net docker repo change. dotnet/dotnet-docker#2375
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
.NET Docker Repo Name Change
Coinciding with the release of .NET 5.0, all Docker tags for .NET Core 2.1/3.1 and .NET 5.0 will be published to one set of unified Docker repositories. The names of these repositories have been changed from the originals to no longer include "core" in the name. For backwards compatibility, the original repositories will continue to be maintained for the supported lifetime of the tags contained within those repositories.
Details
This repository name change is being done in order to better align with the .NET 5.0 branding. But it does apply to .NET Core 2.1 and 3.1 as well in order to allow for a consistently named set of repositories to be used across all versions when migrating to .NET 5.0.
In all of the new repositories, the
latest
tag refers to .NET 5.0 while the original repositories will still continue to have thelatest
tags refer to .NET Core 3.1.Related Issues
The text was updated successfully, but these errors were encountered: