Avoid to capture syscalls for container wherein sysdig runs
Hi,
I use a lot sysdig inside the docker from dockerhub. It works well but as I don't want to print or record in a capture the syscalls of the container wherein sysdig runs, I've to add filters like container.id!={sysdig.container.id} or container.name!={sysdig.container.name} which is not always convenient.
I thought of usage of an argument to tell to sysdig to do not trace syscalls from its own container. For example we could have --not-self as argument or maybe we could use special values for filters : container.id!=%self.container.id, container.name!=%self.container.name.
Regards,
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.