mirror of
https://github.com/containers/fuse-overlayfs.git
synced 2025-08-03 18:05:58 -04:00
README.md: add more information
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
This commit is contained in:
parent
54d1c2157f
commit
b49ce8e958
27
README.md
27
README.md
@ -1,11 +1,32 @@
|
|||||||
containerfs
|
containerfs
|
||||||
==========
|
===========
|
||||||
|
|
||||||
An over complex implementation of overlay in FUSE.
|
An implementation of overlay+shiftfs in FUSE for rootless containers.
|
||||||
|
|
||||||
|
Known issues:
|
||||||
|
=======================================================
|
||||||
|
|
||||||
|
A known issue is that containerfs reports a different inode even
|
||||||
|
if the inode on disk is the same, as with hard links.
|
||||||
|
|
||||||
|
The current implementation keeps in memory the entire tree of the
|
||||||
|
lower directories. A side effect is that modifications to the
|
||||||
|
lower layers is never propagated to the merged directory. Overlayfs
|
||||||
|
doesn't allow changes to the layers as well, altough since there is
|
||||||
|
not such caching done, changes are usually propagated.
|
||||||
|
|
||||||
|
Read-only mode is not supported, so it is always required to specify
|
||||||
|
an upperdir and a workingdir.
|
||||||
|
|
||||||
Usage:
|
Usage:
|
||||||
=======================================================
|
=======================================================
|
||||||
|
|
||||||
```
|
```
|
||||||
./containerfs -o lowerdir=lowerdir/a:lowerdir/b,upperdir=up,workdir=workdir merged
|
$ containerfs -o lowerdir=lowerdir/a:lowerdir/b,upperdir=up,workdir=workdir merged
|
||||||
|
```
|
||||||
|
|
||||||
|
Specify a different UID/GID mapping:
|
||||||
|
|
||||||
|
```
|
||||||
|
$ containerfs -o uid=0:10:100:100:10000:2000,gid=0:10:100:100:10000:2000,lowerdir=lowerdir/a:lowerdir/b,upperdir=up,workdir=workdir merged
|
||||||
```
|
```
|
||||||
|
Loading…
x
Reference in New Issue
Block a user