Does anyone already installed NeuVector in Rancher Desktop? I tried to install using the manifests and helm. For both methods the enforcer pod keeps crashing.

pod/neuvector-enforcer-pod-4qjdl               0/1     CrashLoopBackOff

This is the enforcer pod logs and this is the moment that the pod fails.

2023-03-23T20:48:43.574|INFO|AGT|main.waitForAdmission: Node admission is enabled
2023-03-23T20:48:43.574|INFO|AGT|main.waitForAdmission: Sending join request
2023-03-23T20:48:43.575|INFO|AGT|cluster.newGRPCClientTCP: Expected server name - cn=NeuVector
2023-03-23T20:48:43.578|INFO|AGT|main.waitForAdmission: Agent join request accepted
2023-03-23T20:48:43.581|INFO|AGT|main.main: Runtime storage driver - name=overlayfs
2023-03-23T20:48:43.581|INFO|AGT|dp.Open:
2023-03-23T20:48:43.596|INFO|AGT|probe.New:
2023-03-23T20:48:43.596|ERRO|AGT|probe.NewFileAccessCtrl: FA: Initialize - error=function not implemented
2023-03-23T20:48:43.596|INFO|AGT|probe.New: PROC: Process control is not supported
2023-03-23T20:48:43.605|INFO|AGT|main.(*Bench).RerunKube:
2023-03-23T20:48:43.608|ERRO|AGT|system.(*SystemTools).CheckHostProgram: Done - error=exit status 255 msg=Failed to run script: ret=1

2023-03-23T20:48:43.608|ERRO|AGT|main.(*Bench).checkRequiredHostProgs: - error=exit status 255 program=kubectl
2023-03-23T20:48:43.609|ERRO|AGT|main.(*Bench).RerunKube: Cannot run master node CIS benchmark - error=kubectl command not found.

2023-03-23T20:48:43.614|INFO|AGT|main.(*Bench).RerunKube: Not a kubernetes worker node
2023-03-23T20:48:43.618|ERRO|AGT|fsmon.NewFileWatcher: Open fanotify fail - error=function not implemented
2023-03-23T20:48:43.618|INFO|AGT|probe.(*Probe).netlinkProcMonitor: PROC: Start real-time process listener
2023-03-23T20:48:43.618|ERRO|AGT|main.main: Failed to open file monitor! - error=function not implemented
2023-03-23T20:48:43|MON|Process agent exit status 254, pid=9363
2023-03-23T20:48:43|MON|Process agent exit with non-recoverable return code. Monitor Exit!!
2023-03-23T20:48:43|MON|Kill dp with signal 15, pid=9362
Leave the cluster
2023-03-23T20:48:43|DEBU|dp0|dp_data_thr: dp thread exits
2023-03-23T20:48:43.651Z [INFO]  agent.client: client starting leave
2023-03-23T20:48:44.237Z [INFO]  agent.client.serf.lan: serf: EventMemberLeave: 10.42.0.10 10.42.0.10
2023-03-23T20:48:47.817Z [INFO]  agent: Requesting shutdown
2023-03-23T20:48:47.817Z [INFO]  agent.client: shutting down client
2023-03-23T20:48:47.840Z [INFO]  agent: consul client down
2023-03-23T20:48:47.840Z [INFO]  agent: shutdown complete
2023-03-23T20:48:47.840Z [INFO]  agent: Stopping server: address=127.0.0.1:8500 network=tcp protocol=http
Graceful leave complete
2023-03-23T20:48:47.841Z [INFO]  agent: Waiting for endpoints to shut down
2023-03-23T20:48:47.841Z [INFO]  agent: Endpoints down
2023-03-23T20:48:47.841Z [INFO]  agent: Exit code: code=0
2023-03-23T20:48:47|MON|Clean up.

This is the describe output

Events:
  Type     Reason     Age                   From               Message
  ----     ------     ----                  ----               -------
  Normal   Scheduled  11m                   default-scheduler  Successfully assigned neuvector/neuvector-enforcer-pod-4qjdl to lima-rancher-desktop
  Normal   Pulling    11m                   kubelet            Pulling image "<http://docker.io/neuvector/enforcer:5.0.4|docker.io/neuvector/enforcer:5.0.4>"
  Normal   Pulled     10m                   kubelet            Successfully pulled image "<http://docker.io/neuvector/enforcer:5.0.4|docker.io/neuvector/enforcer:5.0.4>" in 22.298088477s (22.298104263s including waiting)
  Normal   Created    7m50s (x5 over 10m)   kubelet            Created container neuvector-enforcer-pod
  Normal   Started    7m50s (x5 over 10m)   kubelet            Started container neuvector-enforcer-pod
  Normal   Pulled     6m4s (x5 over 10m)    kubelet            Container image "<http://docker.io/neuvector/enforcer:5.0.4|docker.io/neuvector/enforcer:5.0.4>" already present on machine
  Warning  BackOff    68s (x34 over 9m45s)  kubelet            Back-off restarting failed container

Any idea why is this happening?

I think the problem is that

fanotify

support requires Alpine 3.17+ and the Rancher Desktop image is still 3.16 because the 3.17 image on aarch64 doesn't work with Apple's virtualization framework.

Hey @fast-garage-66093 thank you so much for your response. Sure I will open a bug in Github.

I don't need the reference, I get email for all issues filed or updated 😄 But thank you for creating the issue!

Great! Thank you for your help!