The nature of a docker container is to start up, run a task, then go away. It is uninterested in whatever service you want to run that is expected to be available to clients. In order to keep the container running you need to give it something to do when you create the container. This can be done with 2 simple lines of powershell.
## This string, when run by the container, will grab a script from microsoft and run it. $ps = "Invoke-WebRequest -Uri 'https://raw.githubusercontent.com/Microsoft/Virtualization-Documentation/master/windows-server-container-tools/Wait-Service/Wait-Service.ps1' -OutFile 'c:\Wait-Service.ps1';c:\Wait-Service.ps1 -ServiceName WinRm -AllowServiceRestart" ## This will start the container and feed it the string above then while capturing the containerID that you'll want for later ($cid = docker run -d microsoft/windowsservercore powershell.exe -executionpolicy bypass $ps) ## While were at it, lets get the name of the container, it will come in handy as well ($name = (((docker $dkrRemote ps --no-trunc -a| Select-String $cid).ToString()).Normalize()).Split(" ")[-1])
The Wait-Service.ps1 file is provided by Microsoft via github. Since this is a hosted file and could change, I would recommend downloading it and storing it on a web server you control to avoid unplanned changes. Another alternative is to download the file and include it as part of your image build process and skipping the Invoke-webrequest part.
The variable $cid holds the ContainerID which is very useful for copying over files and restarting a container, etc.
You of course can substitute in any container image you like. I prefer to work with a clean container.