Giuseppe Scrivano

FUSE itself keeps same caches, and when we do the look up we must specify for how long the inode is valid. There is a way to invalidate a single...

definitely. We can add such a feature. Would you mind to open a PR to add it?

I am closing this issue since there was no feedback for more than a year

closing the issue since there was no feedback.

the reason for that is that `fchmodat` doesn't support `AT_SYMLINK_NOFOLLOW`. Going through `/proc` is the only workaround I've found to that limitation

we could probably add a test when `fuse-overlayfs` starts and if there is a upperdir directory specified then we also check that `/proc/self/fd/X` can be opened with `O_WRONLY`. What do...

and finally opened a PR: https://github.com/containers/fuse-overlayfs/pull/372

that sets noacl on every mount. Can you please show the options passed to the fuse-overlayfs process? Is `noacl` listed?

could you edit your `storage.conf` file and add `noacl` to the list of mount options (`mountopt`)?

you need to edit the `~/.config/containers/storage.conf` file. I am closing this issue since I could reproduce locally and the proposed fix solved it for me. Please reopen if the issue...