Dockertools: Windows Containers debugging support

Created on 25 Mar 2017 · 8Comments · Source: microsoft/DockerTools

I can't seem to be able to get debugging to work with Windows Containers from Visual Studio 2017. Is this something that could work?

Visual Studio persists in downloading and mapping ClrDbg for -RuntimeID debian.8-x64 even with "com.microsoft.visualstudio.targetoperatingsystem=windows" and even though Visual Studio attempts to start msvsmon in this case, none of the nanoserver images have it and mapping it or copying it over, msvsmon appears to be only capable of exiting instantly.

stale

Source

ericwj

Most helpful comment

@sergiomcalzada FYI: Debugging in windows nano containers is now supported with latest VS2017 pre-release.
See here:
https://blogs.msdn.microsoft.com/dotnet/2017/05/10/announcing-net-core-2-0-preview-1/
https://blogs.msdn.microsoft.com/visualstudio/2017/05/10/update-to-visual-studio-2017-and-next-preview/

prochnowc on 17 May 2017

👍2

All 8 comments

We do support ASP.NET 4.5+ to run in Windows server container with VS 2017 RTW, but ASP.NET Core is not supported yet. We're working on the support for ASP.NET Core to run in Nano server container now.

dazhao-msft on 25 Mar 2017

👍1

Looking forward to it. So it's not supported, but could it work with ClrDbg RuntimeID win7-x64? I could try to lie to Visual Studio that I'm running Linux and have it start ClrDbg with FROM microsoft/dotnet:1.1.1-sdk-nanoserver, or is that somehow blocked or inadvisable?

ericwj on 26 Mar 2017

@dazhao-msft So far i managed to build a windows container for my .NET core app but it doesnt start msvsmon (it simply exits) - i assume right now msvsmon does not support windows server nano.. is that right?

prochnowc on 4 May 2017

Same problem here.

I mounted the msvsmon to the container, but it does not run inside nanoserver image

sergiomcalzada on 10 May 2017

prochnowc on 17 May 2017

👍2

Thanks!
The problem is that while the tools are in preview I can't recommend them to my dev team :(
I will give a try to the preview in my personal computer for now

sergiomcalzada on 18 May 2017

Great! Docker just started working on enabling remote access, which will (hopefully) make this interesting other than on localhost as well.

ericwj on 18 May 2017

This issue is being closed as an inactive issue. If you wish to keep it active, please re-open with any additional context for our consideration, we are happy to take a look!