New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fanotify events do not work between containers #309
Comments
same problem here |
It seems like fanotify does not work across namespaces or bind mounts. https://www.spinics.net/lists/kernel/msg2110225.html But I am really not familiar with it. |
any news on this? events generated from a container in mounted dir/volume are not detected from fanotify running on host or same container |
See the message above; looks like this is a limitation of the kernel |
matthewsilva
pushed a commit
to matthewsilva/dirmon
that referenced
this issue
Apr 28, 2020
Added Mount-based recursive directory monitoring (NOTE: The mount-based monitoring does not behave as expected yet, see docker/for-linux#309 and https://www.spinics.net/lists/kernel/msg2110225.html) (NOTE: Mount-based monitoring currently only monitors the recurisve file tree when accessed through the newly created mount in /temp/dirmon, which makes this useless as of right now. Looking for a workaround because mount-based monitoring is the only easy way to do recursive monitoring without having to do our own recursive mark-building in every provided directory)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behavior
fanotify events are emitted for shared volumes in all containers using that volume
Actual behavior
fanotify events for shared volumes do not propagate from one container to another, or from host to container
Steps to reproduce the behavior
Create a container with a directory mounted from host. Create or modify any file in that directory on host. No fanotify events are emitted in container.
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.)
The text was updated successfully, but these errors were encountered: