[ https://issues.apache.org/jira/browse/MESOS-7580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16895849#comment-16895849 ]
James Peach commented on MESOS-7580: ------------------------------------ I think that MESOS-9900 is related to this request. In MESOS-9900, any changes to the overlayfs upperdir will be charged to the container disk quota. > Use root fs as lower RO layer and container fs as upper layer > ------------------------------------------------------------- > > Key: MESOS-7580 > URL: https://issues.apache.org/jira/browse/MESOS-7580 > Project: Mesos > Issue Type: Wish > Components: containerization > Reporter: Mikhail Lesyk > Priority: Major > > See example: > {code} > mkdir -p rootfs/{opt,container,workdir,result} > mount -t overlay -o > lowerdir=rootfs,upperdir=rootfs/container,workdir=rootfs/workdir none > rootfs/result > touch rootfs/result/opt/trash > umount rootfs/result > ls -a rootfs/opt/ > . .. > {code} > Where rootfs - imaginary root filesystem > rootfs/opt - variable directory on that filesystem > rootfs/container - container work dir > rootfs/result - result overlayfs mountpoint(root fs from container point of > view) > So, any change under rootfs/result will be not visible from rootfs point of > view and it will remain clean, so every container could have own snapshot of > host's root filesystem, but changes would be individual. -- This message was sent by Atlassian JIRA (v7.6.14#76016)