Release Notes for Containers
Chapter 1. New Features in .NET Core 2.1 Containers
The .NET Core 2.1 Release Notes for Containers is an extension of the .NET Core 2.1 Release Notes for RPMs. See .NET Core 2.1 Release Notes for RPMs for information on known issues, the operating system architecture, privacy, and support.
1.1. New Features
.NET Core 2.1 runtime image:
.NET Core 2.1 source-to-image builder image:
Chapter 2. Environment Variable Updates
The following environment variables have been added or removed for .NET Core 2.1 image.
2.1. New Variables
DOTNET_TOOLS Used to specify a list of .NET tools to install before building the app. It is possible to install a specific version by post pending the package name with
2.2. Variables Removed
DOTNET_ASPNET_STORE Publish assuming the runtime image contains the ASP.NET Core runtime store.
See Environment Variables for the list of environment variables available with .NET Core 2.1.
Chapter 3. Known Issues
Build containers for Red Hat Enterprise Linux 7 have been updated to contain the
rh-nodejs10package instead of the
rh-nodejs8package. Support for Node.js 8 will be going end-of-life in December, 2019, and several modules that it installs have security vulnerabilities that will not be fixed. The update to use
rh-nodejs10may break applications that depend on the
rh-nodejs8package. See the Node.js 10 changelog file for more information about relevant changes.
ASP.NET Core applications published as framework-dependent fail to run with
dotnet/dotnet-21-runtime-rhel7because the ASP.NET Core shared framework is missing. See Shared Framework issue in .NET Core 2.1 Release Notes for RPMs for more information.
.NET Core SDK 2.1.3xx contains an incorrect
NETStandard.Libraryversion. Using this SDK version may result in build failures. To correct this issue, update to SDK 2.1.402 (or later). To update to the latest SDK version, change the
DOTNET_SDK_VERSIONenvironment variable to 2.1.402 (or to the latest preferred SDK version or the setting
latest). For more information about this and other environment variables, see Section 2.3., Environment Variables.
If there is a
global.jsonfile that specifies the SDK version and you do not want to update to the latest SDK version, you can work around this issue by removing the following entry in the
See Chapter 7, Known Issues in the .NET Core 2.1 Release Notes for RPMs for a list of known issues and workarounds for RPMs.
Appendix A. Revision History
Added new feature about support for building Visual Basic (VB) and F# projects
Added known issue for SDK 2.1.3xx