.NET Core latest Docker tags updated to 3.1
#3662
Replies: 3 comments
-
|
I tried yesterday and again today to pull and use the Debian 10 '3.1.100' SDK image and get i/o timeout errors pulling image configuration. The 3.0.100 image reference does not do this. Error: Image reference being used is:
Anyone else run into this? |
Beta Was this translation helpful? Give feedback.
-
|
@4deeptech , I have not had any issues. I'd suggest reporting the issue at https://github.com/microsoft/containerregistry. |
Beta Was this translation helpful? Give feedback.
-
|
This is using VSCode remote containers with Docker Desktop. I just now switched my docker file back to:
and it fired right up. I will report this over there and see if anyone knows anything about this. Thanks. |
Beta Was this translation helpful? Give feedback.
-
.NET Core
latestDocker tags updated to 3.1The
latesttags for the dotnet/core repos have been updated to reference .NET Core 3.1.Details
The
latesttags for the dotnet/core repos are always intended to reference the latest supported version of .NET Core. At this time, the latest supported version is .NET Core 3.1. This version of .NET Core is also a long-term supported (LTS) release.The following Docker repos have been updated:
It is recommended to use a more-specific tag than
latestfor anything other than casual development. Once you have an application that you believe will eventually go to production, you are recommended to use a tag like3.1.Beta Was this translation helpful? Give feedback.
All reactions