[
https://issues.apache.org/jira/browse/MESOS-7580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Lesyk updated MESOS-7580:
---------------------------------
Description:
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.
was:
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/crap
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.
> 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
>
> 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
(v6.3.15#6346)
