Problem when tracing the process inside the container.

When tracing the function in the containerized app with ```funclatency.py``` (locally compiled bcc recently), we find that userspace function/libc can indeed be hooked but not triggered for calculating the latency. But the flamegraph indeed see a huge amount of the related function call.

This phenomenon does not appear on the host environment, so I was wondering is there anything wrong with the containerization?

Start with funclatency.py and reproduce the userspace-function tracing comparison in the containerized app and on the host. Check why hooked libc functions are not contributing to latency while the flamegraph shows calls; done means the discrepancy is explained and the container behavior is corrected or documented with a verified test.

Written by the indexing model from the issue text.