<p>Below is my Pod manifest:</p>
<pre><code>apiVersion: v1
kind: Pod
metadata:
  name: pod-debian-container
spec:
      containers:
      - name: pi
        image: debian
        command: [&quot;/bin/echo&quot;]
        args: [&quot;Hello, World.&quot;]
</code></pre>
<p>And below is the output of &quot;describe&quot; command for this Pod:</p>
<pre><code>C:\Users\so.user\Desktop&gt;kubectl describe pod/pod-debian-container
Name:         pod-debian-container
Namespace:    default
Priority:     0
Node:         minikube/192.168.49.2
Start Time:   Mon, 15 Feb 2021 21:47:43 +0530
Labels:       &lt;none&gt;
Annotations:  &lt;none&gt;
Status:       Running
IP:           10.244.0.21
IPs:
  IP:  10.244.0.21
Containers:
  pi:
    Container ID:  cri-o://f9081af183308f01bf1de6108b2c988e6bcd11ab2daedf983e99e1f4d862981c
    Image:         debian
    Image ID:      docker.io/library/debian@sha256:102ab2db1ad671545c0ace25463c4e3c45f9b15e319d3a00a1b2b085293c27fb
    Port:          &lt;none&gt;
    Host Port:     &lt;none&gt;
    Command:
      /bin/echo
    Args:
      Hello, World.
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Mon, 15 Feb 2021 21:56:49 +0530
      Finished:     Mon, 15 Feb 2021 21:56:49 +0530
    Ready:          False
    Restart Count:  6
    Environment:    &lt;none&gt;
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-sxlc9 (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  default-token-sxlc9:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-sxlc9
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  &lt;none&gt;
Tolerations:     node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                 node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                   From               Message
  ----     ------     ----                  ----               -------
  Normal   Scheduled  15m                   default-scheduler  Successfully assigned default/pod-debian-container to minikube
  Normal   Pulled     15m                   kubelet            Successfully pulled image &quot;debian&quot; in 11.1633901s
  Normal   Pulled     15m                   kubelet            Successfully pulled image &quot;debian&quot; in 11.4271866s
  Normal   Pulled     14m                   kubelet            Successfully pulled image &quot;debian&quot; in 11.0252907s
  Normal   Pulled     14m                   kubelet            Successfully pulled image &quot;debian&quot; in 11.1897469s
  Normal   Started    14m (x4 over 15m)     kubelet            Started container pi
  Normal   Pulling    13m (x5 over 15m)     kubelet            Pulling image &quot;debian&quot;
  Normal   Created    13m (x5 over 15m)     kubelet            Created container pi
  Normal   Pulled     13m                   kubelet            Successfully pulled image &quot;debian&quot; in 9.1170801s
  Warning  BackOff    5m25s (x31 over 15m)  kubelet            Back-off restarting failed container
  Warning  Failed     10s                   kubelet            Error: ErrImagePull
</code></pre>
<p>And below is another output:</p>
<pre><code>C:\Users\so.user\Desktop&gt;kubectl get pod,job,deploy,rs
NAME                       READY   STATUS             RESTARTS   AGE
pod/pod-debian-container   0/1     CrashLoopBackOff   6          15m
</code></pre>
<p>Below are my question:</p>
<ul>
<li>I can see that Pod is running but Container inside it is crashing. I can't understand &quot;why&quot; because I see that Debian image is successfully pulled</li>
<li>As you can see in &quot;kubectl get pod,job,deploy,rs&quot; output, <code>RESTARTS</code> is equal to 6, is it the Pod which has restarted 6 times or is it the container?</li>
<li>Why 6 restart happened, I didn't mention anything in my spec</li>
</ul>

<p>This looks like a liveness problem related to the CrashLoopBackOff have you cosidered taking a look into this blog it explains very well how to debug the problem <a href="https://managedkube.com/kubernetes/pod/failure/crashloopbackoff/k8sbot/troubleshooting/2019/02/12/pod-failure-crashloopbackoff.html" rel="nofollow noreferrer">blog</a></p>
