danielpacak
commented
2 years ago Beyond that, having readiness logic spread across Go code and entrypoint.sh is not applicable to the release tarball that only contains tracee-epbf and tracee-rules executable binaries without entrypoint.sh.
It seems that we used tracee.pid file along with a Bash script snippet in the entrypoint.sh as a readiness check when compiling the BPF object was part of tracee-ebpf logic.
Things have changed and we no longer compile BPF nor use tracee.pid in entrypoint.sh as readiness check. What's more, tracee.pid is created early on when tracee-ebpf starts and cannot be considered as reliable readiness check as shown in #1540.