Steps to reproduce:
Start Visual Studio.
Create a new ASP.NET Core 1.1 Web App (I named mine WebApplication1) with Docker support enabled by selecting the appropriate checkbox on the New Project dialog (no changes were made against the default app which was created).
Click on the "Run Docker" button on the Visual Studio toolbar.
Eventually, the Docker container creation fails with the two (2) error dialogs (CLRDBG and an HRESULT error code, both dialogs are attached to this issue).
The Debut Output tool window claims that 'clrdbg/clrdbg' is not found (a screen shot of this tool window is attached).
Docker for Windows is installed on my system. The 'C:' drive is shared.
This is a relatively new install of both Visual Studio 2017 RC and Docker for Windows. Both were installed today.
Added a solution by Adam Joseph Cook · Feb 10 at 12:27 AM
I (with a ton of David's help) found a fix to this issue, at least in my case.
First things, first. I have all of the updates for Visual Studio 2017 RC. My version is now 15.0.0-RC4+26206.0. The last Visual Studio update seems to have fixed Mike Yeager's error (wrong Docker image description).
The main issue was a piece of software that I had installed on my computer, Cadence OrCad (http://www.orcad.com/products/orcad-lite-overview), had added a user environment variable called 'HOME' and set this variable to 'C:\Users\adamj\AppData\Roaming\SPB_16.6'. This variable was seemingly causing issues when the Docker volume mapping was being performed.
Once I removed this 'HOME' variable completely and restarted my computer, Docker worked with a fresh ASP.NET Core 1.1 Web App right out of the box. I did not have to do any modifications to any of the artifacts generated by Visual Studio. No errors. No problems.
Added a solution by Christian Melendez · Mar 21 at 05:10 AM
I just tried again and got the same error, then after reading all the suggestions from David, I tried again the following:
"please reset credentials of shared drives in Docker for Windows and share the drives again."
and it worked :)
Added a solution by Mike Yeager · Feb 06 at 04:05 PM
I reported the incorrect version # in the .yml file and have been told it will be fixed in the next RC update. I also have a problem every time I move between networks. Fox example, everything will work perfectly while I'm at work, then I go home and it's broken. I fix it there and it works until I go back to work.
Open Settings in Docker and restore to factory defaults. Then reshare your drive(s). This fixes it for me. I assume it has to do with Linux and Windows communicating via network.,
Here is another thing I've had to do lately. It seems to happen when I change networks. When I'm at work, it's fine. When I move to my home network or at another office, I have to do this, then it's fine until I move back to the office or to another network. I imagine it's got to do with Linux and Windows communicating via the network.
Open up Settings in Docker. Reset to factory defaults. Re-share your drive(s). For me, the incorrect .yml file (which I submitted as a bug and have been told is fixed for the next release) and the Docer reset are the only remaining issues.
Migrate ASP.NET core existing app
lightweight loading is slower