<p>I’m getting <code>Failed to pull image</code> because the image pull is timing out, I know the image is there I just think my private registry is slow, is there a way to set a timeout limit on image pulls?</p>

<p>The timeout limit can be controlled with the <code>--runtime-request-timeout</code> option for the <code>kubelet</code> service.</p>

<p><a href="https://kubernetes.io/docs/admin/kubelet/" rel="noreferrer">Official documentation</a> for this:</p>

<blockquote>
  <p>Timeout of all runtime requests except long running request - pull, logs, exec and attach. When timeout exceeded, kubelet will cancel the request, throw out an error and retry later. Default: 2m0s (default 2m0s)</p>
</blockquote>

<p>Even though this is not really visible from the description, this value is still passed down into the <a href="https://github.com/kubernetes/kubernetes/blob/5e442a3f61e1e1eb67323183cfba6540c02a4a54/pkg/kubelet/kubelet.go#L276" rel="noreferrer">RemoteImageService (see source code an Github)</a> which is used to pull the images.</p>

<p>Hope this helps.</p>
