-
Notifications
You must be signed in to change notification settings - Fork 319
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
TracingPolicies do not get applied in WSL2 #2338
Comments
Thanks! Can you please provide a sysdump or the tetragon pod logs? For the sysdump, please see https://tetragon.io/docs/troubleshooting/#automatic-log--state-collection. |
cilium-sysdump-20240417-161018.zip @kkourt attached the sysdump |
Not clear to me what exactly the issue is, I'll add some speculation and notes for future reference We dont' seem to have a proper /procRoot:
But at least in terms of metrics, everything seems fine:
And we do have some entries in the policyfilter map:
But maybe they are namespaced and do not correspond to the real cgroups in the kernel. We also seem to have some
|
What happened?
I am building the
main
branch from my local WSL2 environment andTracingPolicy
andTracingPolicyNamespaced
do not get applied. I am running the following example:Tetragon Version
Tetragon build from 1dee96d7d58b7ccc57e955eb71b4c1e72f87293d
Kernel Version
Linux DESKTOP-KI004JQ 5.15.146.1-microsoft-standard-WSL2 #1 SMP Thu Jan 11 04:09:03 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Kubernetes Version
Client Version: v1.29.1
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.29.2
Bugtool
tetragon-bugtool.tar.gz
Relevant log output
No response
Anything else?
Only
process_events
get captured and no other event gets captured.The text was updated successfully, but these errors were encountered: