.NET 5.0 Release #3679
mthalman
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
.NET 5.0 Release
With the release of .NET 5.0 there comes many changes to the .NET Docker images. We've made improvements to the developer experience, offered more options for your Windows containers, and reduced download sizes.
Support for Windows Server Core Containers
We've listened to your feedback and are now publishing Windows Server Core 2019 Docker images for .NET 5.0. This should free you from needing to maintain your own images based on Windows Server Core to satisfy your application's requirements that Nano Server wasn't able to meet.
Manifest Tags for Linux Containers
In order to allow developers to better operate in a multi-architecture world, we've updated our tagging scheme to provide more multi-arch tags. This means that a single Dockerfile can more easily work across multiple CPU architectures.
Reduced Download Sizes
We constantly have our collective eyes on the size of our Docker images and look for ways to reduce them. With the 5.0 release, we've made improvements aimed at reducing download sizes by sharing more layers amongst images.
Breaking Change: .NET Docker Repo Name Change
Due to the branding change from .NET Core to .NET, we've updated the Docker repository names for our Docker images. You'll need to use these new repository names if you want to be able to access the .NET 5.0 Docker images. We also recommend that you migrate to these new repositories if you're making use of .NET Core 2.1 or 3.1 images, although it's not required.
Breaking Change: Removal of buildpack-deps from SDK Docker images
In order to achieve the reduced download sizes mentioned above, we removed the dependency on
buildpack-deps
parent images for Debian and Ubuntu SDK images. Be sure to read the details on the announcement to see whether you may be affected by this change.Breaking Change: Removal of curl from runtime Docker images
Security vulnerabilities are always a concern when consuming software. In order to reduce the vulnerability surface area in our images, we're no longer installing
curl
in ourruntime
andaspnet
Linux images starting with .NET 5.0.Beta Was this translation helpful? Give feedback.
All reactions