microsoft / microsoft/Windows-Containers

Unable to set disk quota for Windows2025 containers

Open
#587 31 comments 0 reactions 1 assignee View on GitHub

@ntrappe-msft is already working on this.

Since May 29, 2025.

🚀 LTSC 2025 bug
Dominant language
PowerShell
Stars
551
Forks
76
PR merge metrics
No merged PRs in 30d

Description

Describe the bug
We are in the process of upgrading to Windows Server 2025 and our initial testing is showing a regression from Windows Server 2019 by way of failing to set disk quota for containers. Previously, we have been able to enforce disk limit for each container.

To Reproduce

  • docker run -it mcr.microsoft.com/windows/servercore:ltsc2025 powershell in one powershell
  • mountvol.exe /L to get the the Volume GUID for the new container
  • New-FSRMQuota -Path "\\?\Volume{GUID-FROM-ABOVE}\" -Size 10GB
New-FSRMQuota : 0x80045313, A required filter driver is not installed, loaded or ready
for service.
At line:1 char:1
+ New-FSRMQuota -Path "\\?\Volume{d7d5def4-b68d-43dd-b571-9eece130a16c} ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (MSFT_FSRMQuota:Root/Microsoft/.../MSFT_FSR
   MQuota) [New-FsrmQuota], CimException
    + FullyQualifiedErrorId : HRESULT 0x80045313,New-FsrmQuota

Expected behavior
We expect to be able to set the disk limit for the volume the same way as Windows Server 2019. The same set of commands works for WindowsServer2019. If we need to install additional packages, it's unclear what else needs to be installed.

Configuration:

  • Edition: Windows Server 2025 (Core or GUI)
  • Base Image being used: Windows Server Core
  • Container engine: docker
  • Container Engine version [e.g. 22]

Additional context
Add any other context about the problem here.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.