<p>I am having problems with some pod staying in init phase all the time.</p>
<p>I do not see any errors when I run the <code>pod describe</code> command. This is the list of the events:</p>
<pre><code>Events:
  Type     Reason     Age              From                                                   Message
  ----     ------     ----             ----                                                   -------
  Normal   Scheduled  5m               default-scheduler                                      Successfully assigned infrastructure/jenkins-74cc957b47-mxvqd to ip-XX-XX-XXX-XXX.eu-west-1.compute.internal
  Warning  BackOff    3m (x3 over 4m)  kubelet, ip-XX-XX-XXX-XXX.eu-west-1.compute.internal  Back-off restarting failed container
  Normal   Pulling    3m (x4 over 5m)  kubelet, ip-XX-XX-XXX-XXX.eu-west-1.compute.internal  pulling image &quot;jenkins/jenkins:lts&quot;
  Normal   Pulled     3m (x4 over 5m)  kubelet, ip-XX-XX-XXX-XXX.eu-west-1.compute.internal  Successfully pulled image &quot;jenkins/jenkins:lts&quot;
  Normal   Created    3m (x4 over 5m)  kubelet, ip-XX-XX-XXX-XXX.eu-west-1.compute.internal  Created container
  Normal   Started    3m (x4 over 5m)  kubelet, ip-XX-XX-XXX-XXX.eu-west-1.compute.internal  Started container
</code></pre>
<p>I can see this also:</p>
<pre><code>  State:          Running
      Started:      Wed, 23 Sep 2020 09:49:56 +0200
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Wed, 23 Sep 2020 09:49:06 +0200
      Finished:     Wed, 23 Sep 2020 09:49:27 +0200
    Ready:          False
    Restart Count:  3
</code></pre>
<p>If I list the pods, it looks like this:
<code>Error from server (BadRequest): container &quot;jenkins&quot; in pod &quot;jenkins-74cc957b47-mxvqd&quot; is waiting to start: PodInitializing</code></p>
<p>But I am not able to see the specific error. Can someone help?</p>

Bob
<p>The official documentation has several recommendations regarding <a href="https://kubernetes.io/docs/tasks/debug-application-cluster/debug-running-pod/" rel="nofollow noreferrer">Debug Running Pods</a>:</p>
<ul>
<li><p><a href="https://kubernetes.io/docs/tasks/debug-application-cluster/debug-running-pod/#examine-pod-logs" rel="nofollow noreferrer">Examining pod logs</a>: by executing <code>kubectl logs ${POD_NAME} ${CONTAINER_NAME}</code> or <code>kubectl logs --previous ${POD_NAME} ${CONTAINER_NAME}</code> if your container has previously crashed</p>
</li>
<li><p><a href="https://kubernetes.io/docs/tasks/debug-application-cluster/debug-running-pod/#container-exec" rel="nofollow noreferrer">Debugging with container exec</a>: run commands inside a specific container with <code>kubectl exec</code>: <code>kubectl exec ${POD_NAME} -c ${CONTAINER_NAME} -- ${CMD} ${ARG1} ${ARG2} ... ${ARGN}</code></p>
</li>
<li><p><a href="https://kubernetes.io/docs/tasks/debug-application-cluster/debug-running-pod/#ephemeral-container" rel="nofollow noreferrer">Debugging with an ephemeral debug container</a>: Ephemeral containers are useful for interactive troubleshooting when <code>kubectl exec</code> is insufficient because a container has crashed or a container image doesn't include debugging utilities. You can find an example <a href="https://kubernetes.io/docs/tasks/debug-application-cluster/debug-running-pod/#ephemeral-container-example" rel="nofollow noreferrer">here</a>.</p>
</li>
<li><p><a href="https://kubernetes.io/docs/tasks/debug-application-cluster/debug-running-pod/#node-shell-session" rel="nofollow noreferrer">Debugging via a shell on the node</a>: If none of these approaches work, you can find the host machine that the pod is running on and SSH into that host.</p>
</li>
</ul>
<p>You can find more details in the linked documentation.</p>
