<p>I've got a deployment that has a pod that is stuck at :</p>

<p>The <code>describe</code> output has some sensitive details in it, but the events has this at the end:</p>

<pre><code>  ...
  Normal   Pulled                 18m (x3 over 21m)  kubelet, ip-10-151-21-127.ec2.internal  Successfully pulled image "example/asdf"
  Warning  FailedSync             7m (x53 over 19m)  kubelet, ip-10-151-21-127.ec2.internal  Error syncing pod
</code></pre>

<p>What is the cause of this error? How can I diagnose this further?</p>

<hr>

<p>It seems to be repulling the image, however it's odd that it's <code>x10 over 27m</code> I wonder if it's maybe reaching a timeout?</p>

<pre><code>  Warning  FailedSync             12m (x53 over 23m)  kubelet, ip-10-151-21-127.ec2.internal  Error syncing pod
  Normal   Pulling                2m (x10 over 27m)   kubelet, ip-10-151-21-127.ec2.internal  pulling image "aoeuoeauhtona.epgso"
</code></pre>

Chris Stryczynski
<p>The <strong>kubelet</strong> process is responsible for pulling images from a registry.</p>

<p>This is how you can check the <code>kubelet</code> logs:</p>

<pre><code>$ journalctl -u kubelet
</code></pre>

<p>More information about images can be found in <a href="https://kubernetes.io/docs/concepts/containers/images/" rel="nofollow noreferrer">documentation</a>.</p>
