New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support and tests for limiting disk usage #61
Comments
@rhvgoyal Has thoughts about this I believe. I think we can do somethings with xfs to limit size on overlayfs |
docker has a pending patch to limit size of container using xfs project quota with overlay graph driver. Its worth looking at it. |
Overlay now supports quota. |
@rhatdan Internally? Without using XFS? How? I could find a way to get it done. |
Only with XFS. |
We have quota built into storage now for both overlay and devicemapper. CLosing. |
The overlay driver doesn't have any notion of limiting disk usage, and the devicemapper driver lets us specify the size of the thin pool device, but not much more. We should explore implementing a more uniform (and uniformly enforceable) way of managing disk usage, and of putting upper bounds on how much space a container can use.
CCing @mrunalp, who I'm hoping has better insight as to what consumers of a runtime like cri-o actually expect usage limits to mean.
The text was updated successfully, but these errors were encountered: