From bb6b2314596b123a92abe54965686772b5ee3aa5 Mon Sep 17 00:00:00 2001
From: Artak <34246760+mkArtakMSFT@users.noreply.github.com>
Date: Tue, 12 May 2020 11:55:58 -0700
Subject: [PATCH] Added dev-certs related known issue for 5.0 Preview 4

---
 release-notes/5.0/5.0-known-issues.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/release-notes/5.0/5.0-known-issues.md b/release-notes/5.0/5.0-known-issues.md
index d0e17a74..61368282 100644
--- a/release-notes/5.0/5.0-known-issues.md
+++ b/release-notes/5.0/5.0-known-issues.md
@@ -16,6 +16,14 @@ This document lists known issues for **.NET 5 Preview 1 and beyond releases** wh
 
 1. The Microsoft.Windows.Compatibility package references dependencies that are not available at the targeted versions. To workaround, individually reference the packages your project needs. It is tracked by [dotnet/runtime/issues #34351](https://github.com/dotnet/runtime/issues/34351)
 
+
+## ASP.NET Core Runtime
+
+### Preview 4
+
+1. The dotnet-certs tool will corrup the dev-certificate if run in any Docker-enabled scenario. If you create / load any docker-enabled ASP.NET Core project the tool will run automatically to check for a valid certificate, won't find it and will try to recreate it. As a result, it'll leave the certificate in a corrupted state.
+We recommend to create / open any docker-enabled projects while on Preview 4 SDK. This will be fixed in Preview 5. It is tracked by [dotnet/aspnetcore/issues #21733](https://github.com/dotnet/aspnetcore/issues/21733)
+
 ## .NET SDK
 
 ### Preview 1