-
Notifications
You must be signed in to change notification settings - Fork 18.9k
Reporting graph driver storage utilization #15331
Copy link
Copy link
Closed
Labels
area/storageImage StorageImage Storagekind/enhancementEnhancements are not bugs or new features but can improve usability or performance.Enhancements are not bugs or new features but can improve usability or performance.kind/featureFunctionality or other elements that the project doesn't currently have. Features are new and shinyFunctionality or other elements that the project doesn't currently have. Features are new and shiny
Milestone
Description
Metadata
Metadata
Assignees
Labels
area/storageImage StorageImage Storagekind/enhancementEnhancements are not bugs or new features but can improve usability or performance.Enhancements are not bugs or new features but can improve usability or performance.kind/featureFunctionality or other elements that the project doesn't currently have. Features are new and shinyFunctionality or other elements that the project doesn't currently have. Features are new and shiny
It may be interesting, for monitoring purpose, to report the storage utilization of the graph drivers.
The information is already reported by some graph drivers, e.g.
https://github.com/docker/docker/blob/a15b676/daemon/graphdriver/devmapper/driver.go#L73-L86
but it's in an unstructured fashion.
I think each driver should report, total and used (or free, or both used/free) space in such a way that could be reliably monitored by external applications.