BUG: Helm installation fails on K8s cluster

[knrt10]

Cluster Information

• minikube installed with eBPF support. You can find the code at kinvolk/cloud-native-bpf-workshop
• Apart from this, tried installing it on a lokomotive cluster on Azure. It runs on flatcar which has eBPF support.

Steps to reproduce

• As specified in the docs here. Although the docs are outdated so had to use the below steps to install it. Also couldn't find where to file a PR for the change.

kubectl apply -f https://lockc-project.github.io/helm-charts/namespace.yaml
helm repo add lockc https://lockc-project.github.io/helm-charts/
helm install lockc lockc/lockc --namespace kube-system --set lockcd.debug.enabled=true

Error information

thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 38, kind: Unsupported, message: "Function not implemented" }', /root/.cargo/git/checkouts/fanotify-rs-c4e2583b7086e958/323ee7d/src/high_level.rs:138:88
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: map error

Caused by:
    0: failed to create map `ap_mnt_restr` with code -1
    1: Operation not permitted (os error 1)

If I am doing something wrong, can you please guide me with the steps?

[vadorovsky]

Hi! Docs repository is here:

https://github.com/lockc-project/book

I will update the links now. Sorry for the inconvenience!

Regarding the error you posted - seems like the lockc container has troubles with creating BPF maps, even though it's privileged. Which CRI server/implementation are you using?

I will try to reproduce with kinvolk/cloud-native-bpf-workshop

[knrt10]

Thank you for repying @vadorovsky. I was using built-in docker CRI. Also I have created a PR for updating docs lockc-project/lockc-project.github.io#1