Fedora 35 - source-built .NET installed via Fedora native package feed
>dotnet --info .NET SDK (reflecting any global.json): Version: 5.0.104 Commit: ca6b6acadb Runtime Environment: OS Name: fedora
We are proposing a policy change for which NuGet CLI (i.e. NuGet.exe) version is included in the sdk images. The proposal is to align the NuGet CLI version with the version of NuGet bundled within MSBuild and the .NET CLI included in the sdk images.
If you are using the NuGet CLI you may be impacted by this change. If you are using NuGet via MSBuild or the .NET CLI you will not be affected by this change.
|sha256:ac83054b3424623b270bcb14f800447c5fb834837a5a07610e6502b051eedb56||amd64||linux||Debian 10||3.0.3||3.0/runtime-deps/buster-slim/amd64/Dockerfile||dotnet/core/runtime-deps||3/11/2020 13:52|
|3.0.3-buster-slim||amd64||linux||Debian 10||3.0.3||3.0/runtime-deps/buster-slim/amd64/Dockerfile||dotnet/core/runtime-deps||3/11/2020 13:52|
|3.0-buster-slim||amd64||linux||Debian 10||3.0.3||3.0/runtime-deps/buster-slim/amd64/Dockerfile||dotnet/core/runtime-deps||3/11/2020 13:52|
|3.1.2-buster-slim||amd64||linux||Debian 10||3.0.3||3.0/runtime-deps/buster-slim/amd64/Dockerfile||dotnet/core/runtime-deps||3/11/2020 13:52|
|3.1-buster-slim||amd64||linux||Debian 10||3.0.3||3.0/runtime-deps/buster-slim/amd64/Dockerfile||dotnet/core/runtime-deps||3/11/2020 13:52|
|sha256:a06dd4359bed5b56bb2cf90765dd1e97b8a4c66b7634d8732b5fa7640e782560||amd64||linux||Alpine 3.10||3.0.3||3.0/runtime-deps/alpine3.10/amd64/Dockerfile||dotnet/core/runtime-deps||3/11/2020 13:52|
|sha256:ca895ab76f1d3ab95f022cbca076e06b62daebafe61af34212bb3ed1fe982d78,amd64,windows,Windows Server 2016,4.8,4.8/runtime/windowsservercore-ltsc2016/Dockerfile,dotnet/framework/runtime,2020-03-11 13:52:00|
|4.8-20200211-windowsservercore-ltsc2016,amd64,windows,Windows Server 2016,4.8,4.8/runtime/windowsservercore-ltsc2016/Dockerfile,dotnet/framework/runtime,2020-03-11 13:52:00|
|4.8-windowsservercore-ltsc2016,amd64,windows,Windows Server 2016,4.8,4.8/runtime/windowsservercore-ltsc2016/Dockerfile,dotnet/framework/runtime,2020-03-11 13:52:00|
|sha256:4308c89ceac1a04af04590ecc56f2f3784ab1fdd21811a6426766cc817bcf9e5,amd64,windows,"Windows Server, version 1903",3.5,3.5/runtime/windowsservercore-1903/Dockerfile,dotnet/framework/runtime,2020-03-11 13:52:00|
|3.5-20200211-windowsservercore-1903,amd64,windows,"Windows Server, version 1903",3.5,3.5/runtime/windowsservercore-1903/Dockerfile,dotnet/framework/runtime,2020-03-11 13:52:00|
|3.5-windowsservercore-1903,amd64,windows,"Windows Server, version 1903",3.5,3.5/runtime/window|
Releasing .NET Core is a complex process involving many components, dependencies on external systems and different teams. With the growing usage and success of .NET Core, it is critical that we are able to release with confidence. This requires us to take necessary steps to validate each release was completed as expected. Ideally we would always release the product without issues but that has not been the case so far. We need tests in place to identify issues so that they can be addressed as part of the release tic-toc before customers are impacted.
This document describes how to validate .NET Core releases. This document describes at a broad level what should be validated. It is not intended to describe the minute details.
The document breaks down the items to validate into the following broad groups.
There are two metrics that are important to consider when discussing the size of Docker images.
The example commands shown below will work on Windows, MacOS, and Linux.
The .NET Core image tags strive to align with the tagging practices utilized by the Official Images on Docker Hub.
<Major.Minor.Patch Version>-<OS>-<Architecture>- e.g.
<Major.Minor Version>-<OS>-<Architecture>- e.g.
Per requests from the community, PowerShell Core has been added to the .NET Core Docker SDK images. PowerShell Core is a cross-platform (Windows, Linux, and macOS) automation and configuration tool/framework that works well with your existing tools and is optimized for dealing with structured data (e.g. JSON, CSV, XML, etc.), REST APIs, and object models. It includes a command-line shell, an associated scripting language and a framework for processing cmdlets.
If you are new to PowerShell and would like to learn more, we recommend reviewing the getting started documentation.
You can try out PowerShell Core by running the following Docker command:
docker run --rm mcr.microsoft.com/dotnet/core/sdk:3.0 pwsh -c Write-Host "Hello Powershell"
The runtime-deps dockerfile currently has a static list of what the runtime dependencies are. There is no link (e.g. tooling that automatically updates the dependencies) to the actual dependencies the runtime has. Because of this, there is a potential for the Docker image to get out of sync with the runtime. The Docker repo CI includes tests which build a basic self-contained hello world application and runs it in the runtime-deps image but this is not extensive enough to fully validate the right set of dependencies are included in the image.
FROM debian:stretch RUN apt-get update \ && apt-get install -y --no-install-recommends \ ca-certificates \ \