Right now, all nanoserver images have 18 months of support, and this makes sense for SAC versions. However this is also applying now to LTSC versions.

Hence, if someone needs a stable environment (Windows Server 2019 LTSC Hosts) and want to use containers, they are forced to use the servercore images, as nanoserver are out of support.

It makes no sense to have WS2019 with 10y support, and the corresponding nanoserver image with 18m support.

Add Support for Adding Removed Features.

Currently when using an image with a Feature removed, it doesn't seem possible to add this missing feature.

the Install-WindowsFeature Powershell comand can be missing in some images and in others requieres mounting a wim image, which is not possible due to the wimmount.sys driver missing.

Question:
Does Docker for Windows Server 2019 support GUI-based applications?

I want to run a GUI application desktop(With a 3d map inside) in windows container at windows server host.

I feedback Windows Server 2004 and Windows Container issue in https://github.com/microsoft/Windows-Containers/issues/53

stephen-turner say: Docker Enterprise for Windows Server, support is provided by Microsoft.

I don't know where can contact Microsoft with this issue. Could you confirm this issue or provide a contact address for me?

I've tested the new insider preview version of WAC container extension. It seems work well, but too many console windows open and close repeatedly in the desktop mode. It seems like every time WAC access to docker host or HNS related resources, gateway creates a docker or related console apps.

This will allow docker to be used to build consistent deployment WIMs and WinPE images

https://docs.microsoft.com/en-us/officeonlineserver/office-online-server

Currently, we only know the existence of mcr.microsoft.com from documentation, we need a portal for search images with different tags.
Oracle just have a simple one.
https://container-registry.oracle.com

All container network interfaces ("vEthernet (Ethernet)") use MTU 1500 by default. There is no way to configure a default MTU other than 1500, despite Docker and Microsoft documentation which indicates that this should be possible: https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-docker/configure-docker-daemon, https://docs.docker.com/engine/reference/commandline/dockerd/#description.

This is a huge pain point for users running on platforms that require an MTU less than 1500. The only solution at this time is to set the container interface's MTU first thing every time one runs a container, for every container.

Need Edge in a container for automated UI testing

I would like to gather performance metrics from a windows container. Something like this project. https://github.com/google/cadvisor

Many Business Application are dependent on Office to edit files or import/export of ppt or word formats. So adding office support for Containers would be a good idea.

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.

We have legacy .NET based business applications making extensive use of MSDTC. It will be good to have support for this role in containers to enable Lift & Shift scenarios.

HCSShim errors in Docker is very uninformative. The only thing we get is an error code which is mostly unhelpful. Writing additional error information would be very good for debugging. For example I get The parameter is incorrect error from HCS but no idea what that parameter is. You can find complaints similar to this one in Docker GitHub repository.

I would like to have support for the --privileged command on windows containers. I would be nice to have this feature on a build server.

Currently with OS upgrade, customers need to update Dockerfile to use the new base image and rebuild docker image.

It will be a painful process for enterprise rebuild & redeploy containers with existing customers on it.

The new OS should be backward compatible especially considering the semi-annual release cadence.