-
Notifications
You must be signed in to change notification settings - Fork 76
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
[Tracking] Feature/performance parity for process-isolated (shared-kernel) containers vs. Linux containers
enhancementNew feature or requestNew feature or requesttriageNew and needs attentionNew and needs attentionStatus: Open.#653 In microsoft/Windows-Containers;Decouple container base image version from host OS version for process-isolated containers
enhancementNew feature or requestNew feature or requesttriageNew and needs attentionNew and needs attentionStatus: Open.#652 In microsoft/Windows-Containers;CimFS-backed overlay mount performance parity with Linux overlayfs for container image layers
enhancementNew feature or requestNew feature or requesttriageNew and needs attentionNew and needs attentionStatus: Open.#651 In microsoft/Windows-Containers;True PID namespace isolation for process-isolated containers (server silos)
enhancementNew feature or requestNew feature or requesttriageNew and needs attentionNew and needs attentionStatus: Open.#650 In microsoft/Windows-Containers;Syscall/capability-scoped restriction policy for process-isolated containers (seccomp/capabilities parity)
enhancementNew feature or requestNew feature or requesttriageNew and needs attentionNew and needs attentionStatus: Open.#649 In microsoft/Windows-Containers;Uninstall docker leaves executables.
bugSomething isn't workingSomething isn't workingtriageNew and needs attentionNew and needs attentionStatus: Open.#648 In microsoft/Windows-Containers;- Status: Open.#647 In microsoft/Windows-Containers;
- Status: Open.#646 In microsoft/Windows-Containers;
Process.Start() and PowerShell Start-Process hang on newer mcr.microsoft.com/windows/servercore:ltsc2019 / .NET Framework 4.8 LTSC2019 images
bugSomething isn't workingSomething isn't workingtriageNew and needs attentionNew and needs attentionStatus: Open.#645 In microsoft/Windows-Containers;Process-isolated container remains "Running" for exactly TcpTimedWaitDelay after all processes exit, if a loopback TCP connection was closed
bugSomething isn't workingSomething isn't workingtriageNew and needs attentionNew and needs attentionStatus: Open.#644 In microsoft/Windows-Containers;Create a CLI and API like wslc but for Windows containers
enhancementNew feature or requestNew feature or requesttriageNew and needs attentionNew and needs attentionStatus: Open.#643 In microsoft/Windows-Containers;- Status: Open.#642 In microsoft/Windows-Containers;