Containers
-
Extend support for WS2019 nanoserver images
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.
14 votes -
More Elaborate WAC Container Extension Requirements Validation Required
Mostly, the Windows container runs on the process isolation mode. This requirement assumes that current OS build and the target container image version should match, including insider preview. If not, a Hyper-V container used instead.
So the WAC container extension should be aware, validate, and notify the administrator that the current environment meets the requirements. If not, the user confused about the feature. This kind of condition is quite hard to understand, so there should be a clear and concise explanation.
My suggestions are:
- Users can select the base image of the container. Then, container extensions check the system…2 votes -
Does Docker for Windows Server 2019 support GUI-based applications?
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.
1 vote -
Windows Server 2004 use docker-compose create multi NAT network HNS process is CPU high
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?
1 vote -
Bug Report: Flickering Console Windows on WAC Desktop Mode
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.
1 vote -
Support Mounting WIMs in Docker images
This will allow docker to be used to build consistent deployment WIMs and WinPE images
4 votes -
1 vote
-
mcr.microsoft.com should have a portal
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.com4 votes -
Allow configuring a default MTU for all containers
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.
13 votes -
Edge
Need Edge in a container for automated UI testing
27 votes -
Container metrics
I would like to gather performance metrics from a windows container. Something like this project. https://github.com/google/cadvisor
2 votes -
Provide Office Support for Containers
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.
72 votes -
Provide an Internet Explorer docker container: enable UI capability
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.
240 votes -
Show additional meaningful error messages when HCS crashes.
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.
3 votes -
Support for MSDTC
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.
29 votes -
Create microsoft registry and stop using foreign layers
Currently the microsoft images for dotnet, server-core etc.use foreign layers to point to the base layers so they are pulled directly from microsoft, i believe this was done for licensing reasons.
This causes issues running in most 'enterprise' networks where direct internet access is not allowed, the normal solution is something like nexus to proxy remote registries. Foreign layers bypasses this and workarounds like '--allow-nondistributable-artifacts' are cumbersome.
Other companies like Oracle have created there own repos where they can host there own licensed images which is a far simpler solution (https://blogs.oracle.com/weblogicserver/the-oracle-container-registry-has-gone-live).
Is it possible for microsoft to host…
6 votes -
Support for --privileged on windows containers
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.
31 votes -
Support symlinks on mounted volumes in Windows 10 Client and Hyper isolation mode
Today when using Windows Server Containers (--isolation=process) when using a mounted volumes you can create symlinks inside them as you would in any other folder. However when using Hyperv isolation, thous when using Windows 10 container Support, mounted volumes do not support symlinks.
For example:
mklink a.txt b.txt
Inside a mounted volume returns Access Denied error
Symlinks are used by most of the developments tools, like git or npm, so no supporting this is blocking every enterprise that wants to leverage containers for development, thus using Windows 10 client as development operating system.
Another option could be to "just" support…
2 votes -
Support OS upgrade without rebuilding Dockerfile
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.
4 votes -
Mount Block Device Inside Container
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.
5 votes
- Don't see your idea?