You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maybe this is by design...
Say you have a lower filesystem, "/lower" containing a directory "/lower/d" and a file "lower/f".
Then you mount an overlay, "/overlay" using an empty upper filesystem, "/upper".
Then rm -rf /overlay/d /overlay/f.
Using overlay merge -l /lower -u /upper command, in the generated shell script you get
The whiteout file and opaque directory from /upper are moved in after deleting the existing file.
I guess its a simple find 1-liner to find these files and delete them from "/lower" if you don't want them but I wonder if overlayfs-tools should either not copy these files in the first place or provide an option not to copy them.
The text was updated successfully, but these errors were encountered:
This is really odd, I can't reproduce this now! Maybe it was the way I set up my mounts originally. I think the mount point for the overlay might have been within the upper directory, which could have messed things up.
This can be closed if no one can reproduce, but maybe there's an edge case here.
Maybe this is by design...
Say you have a lower filesystem, "/lower" containing a directory "/lower/d" and a file "lower/f".
Then you mount an overlay, "/overlay" using an empty upper filesystem, "/upper".
Then
rm -rf /overlay/d /overlay/f
.Using
overlay merge -l /lower -u /upper
command, in the generated shell script you getThe whiteout file and opaque directory from /upper are moved in after deleting the existing file.
I guess its a simple
find
1-liner to find these files and delete them from "/lower" if you don't want them but I wonder if overlayfs-tools should either not copy these files in the first place or provide an option not to copy them.The text was updated successfully, but these errors were encountered: