Hi Team, I have configured kn8's in hardway on my local system, post to the conf . . .

Kubernetes-Slack Discussions
#1

Azarudeen Mohamed:
Hi Team,
I have configured kn8’s in hardway on my local system, post to the configuration when i tried to run the pods , it is working as expected but when i use replicas attribute container is not getting created required your help on this Please find the error details below for your reference :

FYI : When i tried deployment it is scheduling the replicas on the single master node

Events:
  Type     Reason     Age                From               Message
  ----     ------     ----               ----               -------
  Normal   Scheduled  64s                default-scheduler  Successfully assigned default/tomcat to kubenode02
  Normal   Pulled     15s                kubelet            Successfully pulled image "tomcat" in 44.487824258s (44.487831833s including waiting)
  Normal   Pulling    11s (x2 over 59s)  kubelet            Pulling image "tomcat"
  Normal   Pulled     10s                kubelet            Successfully pulled image "tomcat" in 1.594681589s (1.594699652s including waiting)
  Normal   Created    9s (x2 over 15s)   kubelet            Created container tomcat
  Warning  Failed     9s (x2 over 11s)   kubelet            Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "replicas=3": executable file not found in $PATH: unknown
  Warning  BackOff    8s (x2 over 9s)    kubelet            Back-off restarting failed container tomcat in pod tomcat_default(08aa95ba-c857-4e4a-9278-bb3950cfcf3d)
#2

Rob Thorne:
This is a just a guess, but given the event log from k describe, it sounds like containerd is incorrectly installed or configured on the worker node. You might want to look at the kubelet logs on the teh offending nodes as well.

#3

Azarudeen Mohamed:
Thank you Rob, Let me check on that perspective

#4

Azarudeen Mohamed:
@Rob Thorne, Thank you once again, i revisited my setup and i made node to join before weave setup, that leads to the issue while creating a POD. Now i have removed the node and weave Daemonset and rejoined based on the instructions .

#5

Rob Thorne:
@Azarudeen Mohamed so, it works?

#6

Azarudeen Mohamed:
Yes