How can I connect to a WIndows container using RDP?

Docker Desktop
1

I’m trying to build a Windows Server Core container with a custom installer that has only a GUI installer with no ‘quiet’ option. I figure I could do this with maybe with RDP, but I can’t get RDP to work even though the container says RDP is enabled and running. Below is a run showing what I do to start the container and check for RDP services. Any suggestions on how I can get RDP working?

Start container

PS C:\> docker images
REPOSITORY                             TAG                 IMAGE ID            CREATED             SIZE
mcr.microsoft.com/windows/servercore   10.0.14393.3866     464e8044a8d8        4 weeks ago         11.2GB
PS C:\> docker run -i 464e8044a8d8
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

Check that RDP is enabled in registry - it is…

C:\>powershell -command "Get-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server' -name 'fDenyTSConnections'"
powershell -command "Get-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server' -name 'fDenyTSConnections'"

fDenyTSConnections : 0
PSPath             : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\Sys
                 tem\CurrentControlSet\Control\Terminal Server
PSParentPath       : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\Sys
                 tem\CurrentControlSet\Control
PSChildName        : Terminal Server
PSDrive            : HKLM
PSProvider         : Microsoft.PowerShell.Core\Registry

Look for a listener on RDP port 3389 - none shown…

C:\>netstat -a
netstat -a

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:135            3496df6b0782:0         LISTENING
  TCP    0.0.0.0:5985           3496df6b0782:0         LISTENING
  TCP    0.0.0.0:47001          3496df6b0782:0         LISTENING
  TCP    0.0.0.0:49152          3496df6b0782:0         LISTENING
  TCP    0.0.0.0:49153          3496df6b0782:0         LISTENING
  TCP    0.0.0.0:49154          3496df6b0782:0         LISTENING
  TCP    0.0.0.0:49155          3496df6b0782:0         LISTENING
  TCP    0.0.0.0:49156          3496df6b0782:0         LISTENING
  TCP    [::]:135               3496df6b0782:0         LISTENING
  TCP    [::]:5985              3496df6b0782:0         LISTENING
  TCP    [::]:47001             3496df6b0782:0         LISTENING
  TCP    [::]:49152             3496df6b0782:0         LISTENING
  TCP    [::]:49153             3496df6b0782:0         LISTENING
  TCP    [::]:49154             3496df6b0782:0         LISTENING
  TCP    [::]:49155             3496df6b0782:0         LISTENING
  TCP    [::]:49156             3496df6b0782:0         LISTENING
  UDP    0.0.0.0:5353           *:*
  UDP    0.0.0.0:5355           *:*
  UDP    0.0.0.0:54438          *:*
  UDP    0.0.0.0:58086          *:*
  UDP    127.0.0.1:49304        *:*
  UDP    [::]:5353              *:*
  UDP    [::]:5355              *:*
  UDP    [::]:54438             *:*
  UDP    [::]:58086             *:*

Try starting TermService manually - already started…

C:\>net start TermService
net start TermService
The requested service has already been started.

More help is available by typing NET HELPMSG 2182.

Try running sconfig.cmd, which hangs as shown and never comes up with a menu…

C:\>sconfig
sconfig

C:\>echo off
ERROR: The system was unable to find the specified registry key or value.
♀Microsoft (R) Windows Script Host Version 5.812
Copyright (C) Microsoft Corporation. All rights reserved.

Inspecting system...