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

Hi There,

Can you add the SMTP-Server on the Windows Container?

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.

how we can install software .exe in Container , while creating image. Could you please suggest? if yes. then how we can run bat file as exec

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.

Docker is unable to mount VHD or other block devices inside of a container. This would be useful for isolating several disk related tasks that can cause issues. (This does not require device pass-thru like DDA)

This would allow for Windows Full Flash Update (FFU) image creation to be performed inside of a container.

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 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.

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.

Posting as recommended by MS employee

https://social.msdn.microsoft.com/Forums/en-US/windowscontainers/thread/fd2fef9c-62a5-4ce2-9614-123b8e0b9644/

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.

At the Moment Containers have a single file size limit, which is somewhere between 7 and 8GB. When you have Files bigger then that, you won't be able to create Images. This way all Database usage won't be possible, because Databases are rarely less then 7-8GB in size. Also when you want to use media it might have more then 7-8GB. So it would be great to have no single File size limit in Containers

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

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.

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!

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*