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.
3 votes -
Support Mounting WIMs in Docker images
This will allow docker to be used to build consistent deployment WIMs and WinPE images
2 votes -
Edge
Need Edge in a container for automated UI testing
26 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 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.
238 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 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 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.
26 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 -
Create base container image with MSMQ-Server
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!
154 votes -
Fix Docker load/pull/build issue when Bitlocker is enabled
When running Docker in domain joined computer which has Bitlocker enabled, loading/pulling/building images don't work when group policy "Deny write access to fixed not protected by Bitlocker" is on.
According to Patrick Lang, this is because "This setting indirectly affects containers because we create a VHD for each container's scratch space and format it. Since it's a new disk and not yet encrypted, then Windows will block access to that VHD based on that policy." (https://github.com/Microsoft/Virtualization-Documentation/issues/355#issuecomment-284025671)
Because of this restriction and the fact that our security policy doesn't allow exceptions, I cannot currently properly use Docker in my…
24 votes -
Discrete Device Assignment with Docker
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.
4 votes -
A docker Registry like to store image remotly
Docker registry is server side application that stores and lets you distribute Docker images.
We need a Windows version to manage PS and Dockers images1 vote -
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
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
2 votes -
Getting the same level on information with PS and Docker CLI
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
19 votes
- Don't see your idea?