Windows-Containers
Windows-Containers copied to clipboard
Welcome to our Windows Containers GitHub community! Ask questions, report bugs, and suggest features -- let's work together.
Ever since the removal of foreign layers from Windows images, there's unexpected behavior with respect to the digest of the base Windows layer. When pushing an image to a registry...
**Is it planned to support SmartCardReader class device ?** [Devices in containers on Windows](https://learn.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/hardware-devices-in-containers#hyper-v-isolated-linux-container-support) indicates how to use supported devices in a Windows container. Is it planned/possible/requestable to support SmartCardReader...
**Describe the bug** Creating a short name in a layer doesn't appear to persist in subsequent layers, nor is the short name resolvable when starting the container. **To Reproduce** Given...
Please fill out _all the sections_ below for bug issues, otherwise it'll be closed as it won't be actionable for us to address. **Describe the bug** One of the Authors...
**Describe the bug** I don't want to double post, this bug has already been reported in the AKS Github: [Windows pod stuck in terminating state with subpath in volumemounts](https://github.com/Azure/AKS/issues/4309) I...
**Describe the bug** `kubectl logs some-pod` on pods created after an upgrade from 1.26 to 1.27.14 and from containerd 1.7.0 to 1.7.17 fail with ``` error: You must be logged...
Currently GPU Acceleration within Windows Containers only allow for DirectX and frameworks built on top of it. Please allow for a way for us to leverage 3rd party Vendor specific...
Currently, only a subset of devices can be passed through, with GPUs being one of them (albeit limited with only DirectX based frameworks). With the rise and push of NPU/IPUs...
## Describe the bug: When using the `vpci-location-path://PATH` device string syntax with containerd v1.7.0 to expose an individual GPU to a process-isolated Windows container based on its PCIe location path,...
When using WOW64, C:\Windows\System32 actually points to C:\Windows\SysWow64.