It looks like any moving of a file which comes from the read-only underlying filesystem. It doesn't behave the same when one deletes a file instead of moving.
It seems like it's probably a bug in overlayfs, so I'm adding a task for linux so the kernel team can take a look.
It looks like any moving of a file which comes from the read-only underlying filesystem. It doesn't behave the same when one deletes a file instead of moving.
It seems like it's probably a bug in overlayfs, so I'm adding a task for linux so the kernel team can take a look.