Skip to content
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

Closed
nalind opened this issue Jun 8, 2017 · 6 comments
Closed

Add support and tests for limiting disk usage #61

nalind opened this issue Jun 8, 2017 · 6 comments

Comments

@nalind
Copy link
Member

nalind commented Jun 8, 2017

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.

@rhatdan
Copy link
Member

rhatdan commented Jun 23, 2017

@rhvgoyal Has thoughts about this I believe. I think we can do somethings with xfs to limit size on overlayfs

@rhvgoyal
Copy link
Contributor

docker has a pending patch to limit size of container using xfs project quota with overlay graph driver. Its worth looking at it.

moby/moby#32977

@rhatdan
Copy link
Member

rhatdan commented Oct 13, 2017

Overlay now supports quota.

@Silvanoc
Copy link
Contributor

Silvanoc commented Jul 4, 2018

Overlay now supports quota.

@rhatdan Internally? Without using XFS? How? I could find a way to get it done.

@rhatdan
Copy link
Member

rhatdan commented Jul 5, 2018

Only with XFS.

@rhatdan
Copy link
Member

rhatdan commented Mar 8, 2019

We have quota built into storage now for both overlay and devicemapper. CLosing.

@rhatdan rhatdan closed this as completed Mar 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants