Release Notes for .NET 8.0 containers
Making open source more inclusive
Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.
Providing feedback on Red Hat documentation
We appreciate your feedback on our documentation. Let us know how we can improve it.
Submitting feedback through Jira (account required)
- Log in to the Jira website.
- Click Create in the top navigation bar
- Enter a descriptive title in the Summary field.
- Enter your suggestion for improvement in the Description field. Include links to the relevant parts of the documentation.
- Click Create at the bottom of the dialogue.
Chapter 1. New features
The Release Notes for .NET 8.0 containers is an extension of the Release Notes for .NET 8.0 RPM packages. See Release Notes for .NET 8.0 RPM packages for information about known issues, the operating system architecture, privacy, and support.
Chapter 2. Known issues
NodeJS is no longer included in the .NET 8.0 SDK image.
For information on how to port an application that depends on Node.js from an earlier .NET version to the .NET 8.0 image, see the Porting web applications with NodeJS front-ends to build with .NET 8.0 UBI images Knowledgebase solution.
The random user used by OpenShift Container Platform is no longer added to the
/etc/passwdfile on OpenShift Container Platform 3.11. As a result, the .NET
Environment.UserNameproperty returns an empty string.
DOTNET_FRAMEWORKenvironment variables were removed from the image. Instead, The image now includes exact versions of the .NET framework, the ASP.NET Core frameworks, and the SDK version in the
DOTNET_SDK_VERSIONenvironment variables, respectively..
DOTNET_SSL_DIRSenvironment variable used to load certificates from additional directories is no longer handled by the image entrypoint. The default s2i (source-to-image)
runscripts still process the environment variable. To trust certificates in all cases, use
In .NET 8.0, you can no longer specify the command and its arguments to run in a container as a single string. You need to pass the arguments as separate strings. The new syntax also works for the earlier .NET versions.
For example, instead of
podman run registry.access.redhat.com/ubi8/dotnet-70 “echo hello”, use
podman run registry.access.redhat.com/ubi8/dotnet-80 echo hello.
dnfcommand is not available.
To reduce image size, .NET 8.0 container images use the
ubi-minimalbase image instead of the ubi base image. The
ubi-minimalimage uses the
microdnfcommand as its package manager instead of the
If your Dockerfiles/Containerfiles use the
dnfcommand, you must change them to use the
For more information about the
microdnfcommand, please see the
See Known Issues in the .NET 8.0 Release Notes for .NET 8.0 RPM packages for a list of known issues and workarounds for RPMs.