chore(bpftracebase): bump bpftrace base to 81b099f094d2e6092cfe1317cbaaba0c1bbb614f and bcc 0.8.0

[fntlnz]

• Updated bpftrace to 81b099f094d2e6092cfe1317cbaaba0c1bbb614f
• Updated bcc to 0.8.0
  Signed-off-by: Lorenzo Fontana lo@linux.com

[fntlnz]

@dalehamel PTAL, I just updated the bpftrace to include your latest changes.

[dalehamel]

LGTM, though I want to point out that I'm a bit concerned about the use of a static executable in general, per #51, bpftrace/bpftrace#266, and bpftrace/bpftrace#342

Using the static bpftrace, some scripts will deterministically crash, which really limits the usefulness of kubectl-trace. For instance, not even all of the default scripts included with bpftrace will work :(

I had a PR up #52 that offers an alternative using ubuntu and a dynamic build (using glibc), but it results in a much larger image.

I'll bring this up in slack for a broader discussion on it

[leodido]

As discussed privately, we could consider to ship both the images (static and dynamic) letting the user choose whether to use one or the other via flags.

[dalehamel]

As part of #52 i bumped to v0.9, and the static build is broken upstream. I had to make a number of changes and still haven't gotten it working for static.