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
NOTE: This bug is also causing frequent failures in ginkgo tests for docker.
Bug Report
General Information
Environment description: k3s with docker
vagrant@kubearmor-dev-next:~/accuknox/KubeArmor/tests$ k3s --version
k3s version v1.23.9+k3s1 (f45cf326)
go version go1.17.5
vagrant@kubearmor-dev-next:~/accuknox/KubeArmor/tests$ docker --version
Docker version 20.10.13, build a224086
Kernel version: Linux kubearmor-dev-next 5.15.0-46-generic #49-Ubuntu SMP Thu Aug 4 18:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Try to generate some events. Generally running ksp test suite should be fine.
cd tests/
ginkgo --flake-attempts=5 ksp/ syscalls/
In the above, syscall test suite might fail. If it doesn't, run karmor logs --gRPC=:32767 --operation=syscall --logFilter=all, try to exec into one of the multiubuntu pods created by the above and run:
NOTE: This bug is also causing frequent failures in ginkgo tests for docker.
Bug Report
General Information
Linux kubearmor-dev-next 5.15.0-46-generic #49-Ubuntu SMP Thu Aug 4 18:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
To Reproduce
syscall
test suite might fail. If it doesn't, runkarmor logs --gRPC=:32767 --operation=syscall --logFilter=all
, try to exec into one of the multiubuntu pods created by the above and run:Expected behavior
Should receive logs for audited syscalls.
The text was updated successfully, but these errors were encountered: