Docker build targets included with default Visual Studio templates don't work because HTTPS is half set up

[catmanjan]

Cross post from dotnet/aspnetcore#57181

I couldn't find a Visual Studio Github to report this, but basically the out of the box dotnet templates that most dotnet developers will be using as their first foray into Docker do not work.

The dotnet templates host web services over HTTPS and as such the docker launch target is configured to use SSL, however there is no automatic set up/default creation of development certificates so debugging docker will never work.

If you target something like IIS Express or Kestrel you will be prompted to generate development certificates and Visual Studio will do the registration for you.

[fiveisprime]

Thanks for taking the time to report this!

I'm able to reproduce this on a fresh setup. Looks like either a restart or a manual $ dotnet dev-certs https --trust will fix it, but we should really prevent first time customers from hitting this.

[fiveisprime]

I did a bit more digging and found that this is not limited to container debugging and restarting the browser so it refreshes certificates will also correct the issue.

This is known and being tracked by the .NET folks here: dotnet/core#8588

Again, thanks for reporting this. I'll leave this open for now and see about adding a note in the container tools doc about closing all browser windows and retrying.