Release Notes for .NET 6.0 containers
Abstract
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 input on our documentation. Please let us know how we could make it better. To do so:
For simple comments on specific passages:
- Make sure you are viewing the documentation in the Multi-page HTML format. In addition, ensure you see the Feedback button in the upper right corner of the document.
- Use your mouse cursor to highlight the part of text that you want to comment on.
- Click the Add Feedback pop-up that appears below the highlighted text.
- Follow the displayed instructions.
For submitting more complex feedback, create a Bugzilla ticket:
- Go to the Bugzilla website.
- As the Component, use Documentation.
- Fill in the Description field with your suggestion for improvement. Include a link to the relevant part(s) of documentation.
- Click Submit Bug.
Chapter 1. New features
The Release Notes for .NET 6.0 containers is an extension of the Release Notes for .NET 6.0 RPM packages. See Release Notes for .NET 6.0 RPM packages for information about known issues, the operating system architecture, privacy, and support.
Chapter 2. Known issues
-
ReadyToRun
, which is enabled on a source-to-image build via theDOTNET_PUBLISH_READYTORUN
environment variable, is not supported ons390x
. The build will print a warning and ignore this variable. -
The SDK image contains nodeJS to support building JavaScript front-ends in tandem with the .NET backend. Some JavaScript web front-ends cannot be built on
s390x
andaarch64
due to missing nodeJS packages. .NET 6.0 on
s390x
does not understand memory and cpu limits in containers.In such environments, it is possible that .NET 6.0 will try to use more memory than allocated to the container, causing the container to get killed or restarted in OpenShift Container Platform. As a workaround you can manually specify a heap limit through an environment variable:
MONO_GC_PARAMS=max-heap-size=<limit>
. You should set the limit to 75% of the memory allocated to the container. For example, if the container memory limit is 300MB, setMONO_GC_PARAMS=max-heap-size=225M
.
See Known Issues in the .NET 6.0 Release Notes for .NET 6.0 RPM packages for a list of known issues and workarounds for RPMs.