Issues getting the Calico CRI running (Chap 2.2)

terrence2022

Hello, I'm having trouble launching the basicpod in 2.2, it is stuck on ContainerCreating. It shares the same message as my calico-controller pod (output bellow) and I am not familiar with this error message. I have attempted to do a systemctl restart crio as well as reapply the calico manifest.

I'm in an AWS environment.

Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 11m default-scheduler Successfully assigned calico-system/calico-kube-controllers-666bb9949-2lstp to ip-172-31-17-245
Warning FailedCreatePodSandBox 11m kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_calico-kube-controllers-666bb9949-2lstp_calico-system_5d952fbc-6685-4eb1-bf0a-235f86774922_0(00cbf2961a50b3fa17fe0f4cda52cf3244f39768192889859be50012b37216b5): No CNI configuration file in /etc/cni/net.d/. Has your network provider started?
Warning FailedCreatePodSandBox 11m kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_calico-kube-controllers-666bb9949-2lstp_calico-system_5d952fbc-6685-4eb1-bf0a-235f86774922_0(b0be8e2258989a0410390bcbf276811fbc7a1b2bedb89d37f1e5fc49f408d253): No CNI configuration file in /etc/cni/net.d/. Has your network provider started?
Warning FailedCreatePodSandBox 11m kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_calico-kube-controllers-666bb9949-2lstp_calico-system_5d952fbc-6685-4eb1-bf0a-235f86774922_0(b55b952d62c229cf76c0c6a539c32863acaa84368e28f310739d68aeee1fbe71): No CNI configuration file in /etc/cni/net.d/. Has your network provider started?
Warning FailedCreatePodSandBox 11m kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_calico-kube-controllers-666bb9949-2lstp_calico-system_5d952fbc-6685-4eb1-bf0a-235f86774922_0(f542e72cc36859defd711416c4e406806bda37aa22ffb3d0dd3e58041b828fc7): No CNI configuration file in /etc/cni/net.d/. Has your network provider started?
Warning FailedCreatePodSandBox 11m kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_calico-kube-controllers-666bb9949-2lstp_calico-system_5d952fbc-6685-4eb1-bf0a-235f86774922_0(8d9dd3f699377f9d24e3c0cccbe5e71baa7f19226a4091ab8ab67bb2ab844ea0): No CNI configuration file in /etc/cni/net.d/. Has your network provider started?
Warning FailedCreatePodSandBox 10m kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_calico-kube-controllers-666bb9949-2lstp_calico-system_5d952fbc-6685-4eb1-bf0a-235f86774922_0(a2ca022b1e2593b1ec2f68c58cf583a572af4276ecf6127aa5247c5399c042f2): No CNI configuration file in /etc/cni/net.d/. Has your network provider started?
Warning FailedCreatePodSandBox 10m kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_calico-kube-controllers-666bb9949-2lstp_calico-system_5d952fbc-6685-4eb1-bf0a-235f86774922_0(fb029f5723979f03e50516c4283dfe243f3bb4043424e428c4a78ab518d70ffd): No CNI configuration file in /etc/cni/net.d/. Has your network provider started?
Warning FailedCreatePodSandBox 10m kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_calico-kube-controllers-666bb9949-2lstp_calico-system_5d952fbc-6685-4eb1-bf0a-235f86774922_0(9df1e33e66804b1ddd7dc941a995e633af0b5e9ffbf518d6176b212973899adb): No CNI configuration file in /etc/cni/net.d/. Has your network provider started?
Warning FailedCreatePodSandBox 10m kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_calico-kube-controllers-666bb9949-2lstp_calico-system_5d952fbc-6685-4eb1-bf0a-235f86774922_0(904254e160faac0e077c52e63538ab8ed596a40510ecfe1db07560584497e591): No CNI configuration file in /etc/cni/net.d/. Has your network provider started?

chrispokorni

Hi @terrence2022,

When Calico runs successfully it will allow for other pods to run as well. Did you happen to follow the provisioning steps presented in the video guide found in the introductory chapter? Key networking, VPC, SG, and other configuration options are presented there for AWS EC2 instances. With Calico being a networking component, the issues may be related to the VPC configuration and possibly the SG not allowing through all the required inbound traffic.

Regards,
-Chris

terrence2022

Hi, yes I did, as recommended in the video I used the default VPC and also allowed all inbound traffic across all ports.

sdragnia

Hi terrence2022, I noticed that the lab expects the calico.yaml file to have the IPv4POOL_CIDR and value uncommented. The file has the lines commented out by default. Uncommenting them worked for me:

4222 - name: CALICO_IPV4POOL_CIDR 4223 value: "192.168.0.0/16"

chrispokorni

Hi @sdragnia,

Calico is expected to work in both cases with those two lines commented (defaut) or uncommented.

Regards,
-Chris