none
Running Visual Studio Remote Debugger in Windows Container (Docker managed) RRS feed

  • Question

  • Originally asked on StackOverflow: http://stackoverflow.com/questions/36420337/running-visual-studio-remote-debugger-in-windows-container-docker-managed

    I try to run the Visual Studio Remote Debugger in a Windows Container on Windows Server 2016 TP4. Since it runs inside a container, there is no UI.

    I try to run the remote debugger via:

     .\msvsmon.exe /nostatus /silent /nosecuritywarn /nofirewallwarn /noclrwarn /port 4020
    

    I am executing the above as administrator user (nt authority\system). This works fine on the host computer, but it does not work inside the container. The Windows event log shows the following error event.

    Msvsmon was unable to start a server named "`6D2D071453C5:4020`". 
    The following error occurred: The parameter is incorrect. 
    

    Complete event log:

    Get-EventLog -LogName Application -EntryType Error | format-list
    
    Index              : 1718
    EntryType          : Error
    InstanceId         : 3221226473
    Message            : The description for Event ID '-1073740823' in Source 'Visual Studio Remote Debugger' cannot be found.  The local computer may not have the necessary registry information or message DLL
                         files to display the message, or you may not have permission to access them.  The following information is part of the event:'Msvsmon was unable to start a server named
                         '6D2D071453C5:4020'. The following error occurred: The parameter is incorrect.
    
                         View Msvsmon's help for more information.'
    Category           : (0)
    CategoryNumber     : 0
    ReplacementStrings : {Msvsmon was unable to start a server named '6D2D071453C5:4020'. The following error occurred: The parameter is incorrect.
    
                         View Msvsmon's help for more information.}
    Source             : Visual Studio Remote Debugger
    TimeGenerated      : 05.04.2016 9:47:19 AM
    TimeWritten        : 05.04.2016 9:47:19 AM
    UserName           : NT AUTHORITY\SYSTEM
    

    Now, here comes the confusing part:

    6D2D071453C5 is the container id of my Windows container (docker managed):

    PS C:> docker ps -a
    CONTAINER ID        IMAGE               COMMAND                   CREATED             STATUS                    PORTS               NAMES
    6d2d071453c5        d9d15fbca6d7        "cmd /S /C 'C:\\myprg-"   6 days ago          Up 3 days                                     derrin
    

    Usually, in Docker, this container id will also be the hostname inside/of the container.

    So, when I run docker inspect 6d2d071453c5, I get this in the output:

    "Config": {
        "Hostname": "6d2d071453c5",
        "Domainname": "",
    

    But then, inside the container, I type "hostname" in the command line and get:

    PS C:> hostname
    test2016
    

    I think this is specific to Windows Server 2016 Containers running Windows containers at the moment and not sure if this is a bug.

    The hostname should not be test2016 (the name of the container host, my actual physical Win2016 server) but the container id (6d2d071453c5). At least, this would be my expected behaviour and this is also the case when I run any other container, i.e. a Ubuntu container, on Windows that require a VM. I just re-checked it.

    Nevertheless, to circumvent the issue, I adjust the host file, adding:

    172.16.0.2        6d2d071453c5
    

    Now I can ping my own hostname at least.

    PS C:\Program Files\Microsoft Visual Studio 14.0\Common7\IDE\Remote Debugger\x64> ping 6D2D071453C5
    
    Pinging 6d2d071453c5 [172.16.0.2] with 32 bytes of data:
    Reply from 172.16.0.2: bytes=32 time<1ms TTL=128
    Reply from 172.16.0.2: bytes=32 time<1ms TTL=128
    

    Nevertheless, the remote debugger still does not start, and still says:

    Msvsmon was unable to start a server named "`6D2D071453C5:4020`". 
    The following error occurred: The parameter is incorrect.
    

    I don't see what's wrong with any of the parameters, according to the accompanied help file that lists all the parameters and options. The very same command works fine on the container host, just not inside the container.

    Has anybody gotten the remote debugger to work inside a container?

    Tuesday, April 5, 2016 10:50 AM