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
I've been reading in #70 that we are rightfully concerned about how our File probes are behaving when reporting paths related to an overlay filesystem (container filesystem, non root mount namespace)
I talked with @ferullo and he confirmed that the requirement for "step 1" is to always report the path as it is in the root mount namespace.
In certain circumstances, it could happen that an event is duplicated (e.g: we see both the unlink event in the container mount namespace and in the root mount namespace)
We need to make sure that for file create, rename and delete we only report the root mount namespace events.
The text was updated successfully, but these errors were encountered:
tabell
changed the title
File events: make sure that the reported paths are the ones on root mount namespace
duplicate rename events from mount namespace
Apr 4, 2022
tabell
changed the title
duplicate rename events from mount namespace
investigate duplicate rename events from mount namespace
Apr 4, 2022
I've been reading in #70 that we are rightfully concerned about how our File probes are behaving when reporting paths related to an overlay filesystem (container filesystem, non root mount namespace)
I talked with @ferullo and he confirmed that the requirement for "step 1" is to always report the path as it is in the root mount namespace.
In certain circumstances, it could happen that an event is duplicated (e.g: we see both the unlink event in the container mount namespace and in the root mount namespace)
We need to make sure that for file create, rename and delete we only report the root mount namespace events.
The text was updated successfully, but these errors were encountered: