Limit directory size in a Docker container

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












I have a web application in a Docker container. I need to limit maximum size of some of its directories. When I was not using Docker, I just created disk partitions of the limit size and put those directories to there. But since Docker seems to share disk partitions with the external system (the output of lsblk command inside the container is exactly the same as if performed outside), this approach is not possible.



How to solve this? Is there possibly a tool which check the size of a directory and denies the permission to write if the size extends the limit?







share|improve this question






















  • What about a limited partition like you already did, create desired folders there and mount them with e.g. --volume /limitedpartition/var:/var:rw?
    – mviereck
    Mar 9 at 17:56










  • that is for sure a possibility, but it violates the principle of keeping the deployment as simple as possible - something else needs to be done besides just running the docker image and I would like to avoid this
    – karlosss
    Mar 9 at 23:16














up vote
0
down vote

favorite












I have a web application in a Docker container. I need to limit maximum size of some of its directories. When I was not using Docker, I just created disk partitions of the limit size and put those directories to there. But since Docker seems to share disk partitions with the external system (the output of lsblk command inside the container is exactly the same as if performed outside), this approach is not possible.



How to solve this? Is there possibly a tool which check the size of a directory and denies the permission to write if the size extends the limit?







share|improve this question






















  • What about a limited partition like you already did, create desired folders there and mount them with e.g. --volume /limitedpartition/var:/var:rw?
    – mviereck
    Mar 9 at 17:56










  • that is for sure a possibility, but it violates the principle of keeping the deployment as simple as possible - something else needs to be done besides just running the docker image and I would like to avoid this
    – karlosss
    Mar 9 at 23:16












up vote
0
down vote

favorite









up vote
0
down vote

favorite











I have a web application in a Docker container. I need to limit maximum size of some of its directories. When I was not using Docker, I just created disk partitions of the limit size and put those directories to there. But since Docker seems to share disk partitions with the external system (the output of lsblk command inside the container is exactly the same as if performed outside), this approach is not possible.



How to solve this? Is there possibly a tool which check the size of a directory and denies the permission to write if the size extends the limit?







share|improve this question














I have a web application in a Docker container. I need to limit maximum size of some of its directories. When I was not using Docker, I just created disk partitions of the limit size and put those directories to there. But since Docker seems to share disk partitions with the external system (the output of lsblk command inside the container is exactly the same as if performed outside), this approach is not possible.



How to solve this? Is there possibly a tool which check the size of a directory and denies the permission to write if the size extends the limit?









share|improve this question













share|improve this question




share|improve this question








edited Mar 7 at 8:36

























asked Mar 7 at 8:31









karlosss

20416




20416











  • What about a limited partition like you already did, create desired folders there and mount them with e.g. --volume /limitedpartition/var:/var:rw?
    – mviereck
    Mar 9 at 17:56










  • that is for sure a possibility, but it violates the principle of keeping the deployment as simple as possible - something else needs to be done besides just running the docker image and I would like to avoid this
    – karlosss
    Mar 9 at 23:16
















  • What about a limited partition like you already did, create desired folders there and mount them with e.g. --volume /limitedpartition/var:/var:rw?
    – mviereck
    Mar 9 at 17:56










  • that is for sure a possibility, but it violates the principle of keeping the deployment as simple as possible - something else needs to be done besides just running the docker image and I would like to avoid this
    – karlosss
    Mar 9 at 23:16















What about a limited partition like you already did, create desired folders there and mount them with e.g. --volume /limitedpartition/var:/var:rw?
– mviereck
Mar 9 at 17:56




What about a limited partition like you already did, create desired folders there and mount them with e.g. --volume /limitedpartition/var:/var:rw?
– mviereck
Mar 9 at 17:56












that is for sure a possibility, but it violates the principle of keeping the deployment as simple as possible - something else needs to be done besides just running the docker image and I would like to avoid this
– karlosss
Mar 9 at 23:16




that is for sure a possibility, but it violates the principle of keeping the deployment as simple as possible - something else needs to be done besides just running the docker image and I would like to avoid this
– karlosss
Mar 9 at 23:16















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f428691%2flimit-directory-size-in-a-docker-container%23new-answer', 'question_page');

);

Post as a guest



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes










 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f428691%2flimit-directory-size-in-a-docker-container%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

How to check contact read email or not when send email to Individual?

Bahrain

Postfix configuration issue with fips on centos 7; mailgun relay