Leonardo Di Giovanna
Leonardo Di Giovanna
Hi @camilla-m. I think the problem is due to the kernel version used by your nodes. You could try to downgrade to a lower kernel version: 5.4.0-91-generic should work.
The #439 is a similar question. In the issue, an user advises to use AF_BRIDGE as family. I tried ``` neigh := &netlink.Neigh{ LinkIndex: link.Attrs().Index, State: netlink.NUD_PERMANENT, IP: net.IPv4(10, 225,...
> > The #439 is a similar question. In the issue, an user advises to use AF_BRIDGE as family. I tried > > ``` > > neigh := &netlink.Neigh{ >...
Oh yes, sure!
Done :smile:
Close this in favor of: - https://github.com/falcosecurity/libs/pull/2523 - https://github.com/falcosecurity/libs/pull/2524
Hey! Is there any chance this patch will get considered any soon?
Maybe is just a mistyping issue, but I see you wrote: > - name: https_proxy value: "http://myproxy.com:8080/" Could it be: - name: https_proxy value: "https://myproxy.com:8080/" ?
Linux headers are not required with the modern eBPF driver. Could you please check, by issuing `kubectl describe pod falco-jlrjh`, which init container is crashing and what is the reason?