Install Calico with iptables runs a ebpf-bootstrap container (which fails)

[dozer75]

I try to install calico on my local rancher-desktop instance, I follow the instructions on https://docs.tigera.io/calico/latest/getting-started/kubernetes/self-managed-onprem/onpremises and uses iptables instructions, but when I have applied the custom resources, the calico deployment fails with Pod calico-system/calico-node-bdznj has crash looping container: ebpf-bootstrap (ContainerCannotRun, exit code 128) ...

I can understand that it fails as the environment probably doesn't support eBPF, but why is the setup starting a container that according to the name does eBPF related things when I use iptables?

[caseydavenport]

Yeah, sorry, that container name is misleading. ebpf-bootstrap runs regardless of dataplane - it just mounts the BPF filesystem so it's there if you ever enable eBPF later, and in iptables mode it runs --best-effort so missing BPF support won't fail it. ContainerCannotRun / exit 128 is the runtime failing to start the container before our binary even runs, so it's not an eBPF-support thing - on Rancher Desktop my guess is the bidirectional mount propagation on /sys/fs. Can you post kubectl describe pod calico-node-bdznj -n calico-system and the containerd log? The runc create error should show what it's choking on.