We would like to run selenium tests in isolated displays as is currently possible for Chrome and Firefox in docker-selenium or dosel.

Also, it would be great to video record the entire desktop to troubleshoot failing tests.

Windows Server 2016 added Discrete Device Assignment (DDA) support for Hyper-V. This functionality should be extended to support Windows Containers and most importantly Docker containers using the --device option to expose the device into a container.

This functionality would bring the convenience of Docker containers and enable the use of GPUs, USB devices and other PCI Express devices inside a Docker container.

Please enable "Server" service so container file system can be accessed from host and this is also prerequisite for other UI management tools which are disabled due to that like EventViewer for example

If you login interactively into container and try to list environment variable you passed to container at start up time it will be missing from list.
Reproduction steps.
1. Create container with customer variable (docker run -d -e me=too microsoft/iis)
2. Check value of variable via CMD

PS D:\docker> Exec-Container -ContainerIdOrName 7a -Command @("powershell", "dir env:m*")

Name Value
---- -----
me too
3. Enter interactively and check the same variable
S D:\docker> Enter-PSSession -ContainerId (Get-Container b4).ID -RunAsAdministrator
[b4d8a6624253...]: PS C:\Users\ContainerAdministrator\Documents> dir env:m*

The MSMQ-Server role is a prerequisite for Particular NServiceBus installation. As NServiceBus handlers are potentially a good fit for containerization, it was disappointing to find that it is not possible to install MSMQ-Server in a container. Please create a base image with this support!

More info here: https://social.msdn.microsoft.com/Forums/en-US/b646b841-c9fb-4f39-9662-5b59f02279ab/installing-servermediafoundation-in-a-docker-container?forum=windowscontainers

Please allow us to use the Server-Media-Foundation feature required by certain server workloads like IPTV, IP cameras and Plex Media Server.

In hindsight, running Get-Credential was a bad idea inside the container, but what appears to happen is the command just hangs (presumably waiting for the credential dialog box to get submitted). Trying to 'docker attach' from another shell hangs also - the only remedy is to 'docker stop'.

Currently, only the very latest installer for the Visual studio core tools installs correctly within a container. It would help if the installers for Older versions of Visual Studio (https://www.microsoft.com/en-us/download/details.aspx?id=44266 in particular) shouldn't complain that their executable "is not compatible with the version of Windows you're running." This would help make containers much more useful for running CI tests with older versions of Visual Studio. Some of the older installers even raise that error when being run outside of a container in a full Windows Server TP 4 installation.

Just like we have an mmc to manage h\w-virtualized VM's there should be one for OS-virtualized containers to monitor their resource consumption, health etc...

It would be good if containers could be domain joined for account and security purposes.

Right now, Get-Container does not expose the ip address in use by the container runtime. There is also no alternative cmdlet to figure the ip address out. You need to go in and check.

There should be an MMC to manage and configure windows and Hyper-v containers. This is a Windows component. And like other components there should be a gui to manage it

Today in TP3, Windows container started with PS are not showed if you do a docker ps -a. Windows container run with docker cli are not show in PowerShell with Get-container. Another example : with docker CLI, you work a lot with ID (that you can see with docker ps -a). In PowerShell Get-container doesn't show ID

It would be great to have a mechanism for performing some actions when a container is first created.

One example is devops scenario where a container image is prepared, then when a new container is created from that image and started, it downloads and installs the latest version of the app.

You can create multiple containers with the same name. We need a way to specify a unique attribute during creation so idempotent configurations can check on this. I created a DSC resource which now used the Container Name a key parameter which is contradictive but there is no alternative.

Many of the concepts described involve applications outside of "core" server roles. It would be remarkably cool to see roles such as AD DS run in a container, similar to a FreeBSD jail. This capability would thus allow for a security architecture that isolates components from one another. By going a step further, policy could be defined at the container level to control ingress/egress, manage file system access, etc. Effectively, the server roles are abstracted from the host OS, much as Device Guard and Credential Guard isolate user space and LSASS processes.

Right now you can to enter-pssession directly to a container, but it would be great to be able to use new-pssession and be able to pass that session to other cmdlets like copy-item