Chapter 7. Known issues
The known issues for running .NET on Red Hat Enterprise Linux (RHEL) include the following:
dotnet dev-certs https --trust
does not work on RHEL..NET supports the creation of HTTPS certificate through
dotnet dev-certs https
, but it does not support trusting them throughdotnet dev-certs https --trust
. The client that connects to the ASP.NET Core application, such ascurl
or Firefox, will warn about the untrusted self-signed certificate. To work around this in a browser such as Firefox, ignore the warning and trust the certificate explicitly when the warning about the untrusted certificate comes up. Command-line tools support flags to ignore untrusted certificates. Forcurl
, use the--insecure
flag. Forwget
, use the--no-check-certificate
flag.There are no NuGet packages for
ppc64le
ands390x
on nuget.org.Using the
rhel.8-s390x
,linux-s390x
,rhel.8-ppc64le
, orlinux-ppc64le
runtime identifier can cause somedotnet
commands to fail when they try to obtain these packages. These commands are either not fully supported onppc64le
ands390x
as described in the other known issues, or the issue can be fixed by not specifying the runtime identifier.-
Single file applications are not supported on
ppc64le
ors390x
. -
PublishReadyToRun/crossgen is not supported on
ppc64le
ors390x
. -
OmniSharp, the language server used by IDEs like Visual Studio Code, is not available on
ppc64le
ands390x
. Several workloads not be installed in the .NET 8.0 shipped by Red Hat:
-
android
-
macos
-
maui-android
-
maui-tizen
-
maui-windows
-