Open snoby opened 1 year ago
@snoby, thank you for the report! I have successfully reproduced the issue on the 5.4.0-1092-kvm kernel. It appears that certain tracepoints are disabled in "-kvm" kernels.
grep CONFIG_FTRACE_SYSCALLS "/boot/config-$(uname -r)"
# CONFIG_FTRACE_SYSCALLS is not set
Unfortunately, the agent cannot function without the syscalls/* tracepoints, and currently, no workarounds come to mind.
grep CONFIG_FTRACE_SYSCALLS "/boot/config-$(uname -r)"
Thank you for following up on this. The ubuntu kernel's in AWS does indeed have this feature enabled, i will research if there is a ubuntu cloud image kernel that i can install that has this feature enabled.
Thanks for your help!
Unfortunately, the agent cannot function without the syscalls/* tracepoints, and currently, no workarounds come to mind.
Can we at least add a feature to skip those tracepoints? Like --disable-syscall-tracepoints
. I believe in that case we only loose the service-map. Right?
EDIT: I have tried to change the code to ignore the error. And the agent is working fine and surprisingly I can even see the service-map.
Given the documented docker run line
on a ubuntu 2004 host (not running in k8s) the container starts and immediately exits.
I've verified that the paths are correct, that indeed /sys/kernel/debug and /sys/fs/cgroup does exist on the host.
On the host there is nothing in the
root@db:~# ls /proc/1/root/sys/fs/bpf/
directory.I'm using the latest docker image