Yuval Kohavi
Yuval Kohavi
also relevant to istio CA
This is due to the fact the build is performed using docker, and only the current directory is shared with the container (see [here](https://github.com/solo-io/bumblebee/blob/a78862e1de4a029025fb2f7da5c46c500af5473b/pkg/cli/internal/commands/build/build.go#L194)). cd to the `/tmp` folder and...
weird, works on my linux (5.15.11-200.fc35.x86_64)... could be an arm thing? are the other probes working?
Ahh ok this makes sense; a krpobe that uses the arguments needs to be recompiled for arm, as it uses different registers. I'm surprised recompiling didn't work, as it should...
+ bee should probably validate the architecture of an image before running and emit a warning/error
@nickschuetz try with `-D__TARGET_ARCH_arm64`. this should work for you. you can see the full list in https://github.com/torvalds/linux/blob/78d8b34751cf3c61b8dcd6ac40b0fc453de3c6a3/tools/lib/bpf/bpf_tracing.h#L6
do you have an example for such pr? I'm not sure what do you mean exactly.
because you are running this using docker, the path needs to be accessible form the docker vm in the mac; i'm not sure how mounting the home dir in mac...
yea write to bin_fmt requires root; if there a shell command we can use to do this? this way we can prefix it with sudo. also, how does this work...
i'm open to add systemd-nspawn as an option (even one that's enabled by default, and assuming it works for everyone deprecate the old way). as for registration, it doesn't need...