<p>I am a beginner learning about Kubernetes. I tried pulling an unofficial image from a private registry for zookeeper in my yaml file for testing but the pod status was ImagePullBackOff. Somehow I got that error rectified and the image was pulled successfully but the new error being reflected for pod status is CrashLoopBackOff. Upon using the command &quot;kubectl logs -f -p zookeeper-n1-pod-0 -c zookeeper-n1 -n test-1&quot; or using &quot;kubectl logs podname&quot; command in any way or form in putty terminal, there isn't any output, the cursor just moves to the next line. I tried &quot;exit $?&quot; command to see the exit status of my previous command and got the output as 0 which means that the last command was executed successfully yet I see the pod status as CrashLoopBackOff. I am not able to solve this issue as no logs are present. What is the probable cause and solution for this?</p>
<p>Thanks in advance!!</p>

Dolly
<p>CrashLoopBackOff tells that a pod crashes right after the start. Kubernetes tries to start pod again, but again pod crashes and this goes in loop.</p>
<pre><code>kubectl logs [podname] -p
</code></pre>
<p>the -p option will read the logs of the previous (crashed) instance.</p>
<p>Next, you can check &quot;state reason&quot;,&quot;last state reason&quot; and &quot;Events&quot; Section by describing pod.</p>
<p><code>kubectl describe pod -n</code></p>
<p>I would recommend you to check this blog <a href="https://sysdig.com/blog/debug-kubernetes-crashloopbackoff/" rel="nofollow noreferrer">Debugging CrashLoopBackOff</a></p>
