7

I’m getting Failed to pull image 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?

Simon I
  • 3,406
  • 4
  • 26
  • 32

1 Answers1

6

The timeout limit can be controlled with the --runtime-request-timeout option for the kubelet service.

Official documentation for this:

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)

Even though this is not really visible from the description, this value is still passed down into the RemoteImageService (see source code an Github) which is used to pull the images.

Hope this helps.

pagid
  • 13,559
  • 11
  • 78
  • 104
  • Thank's for the help, it there a way to put this in my deployment manifest? I'm deploying using helm not kubelet. – Simon I Apr 11 '17 at 10:09
  • There's no configuration available to do this through the API anyhow. This has to be configured per node/kubelet. Sorry – pagid Apr 11 '17 at 10:47
  • 2
    Doesn't the doc say "Timeout of all runtime requests except long running request - pull"? Isn't this specifically saying it doesn't apply to pull requests? – MikeKulls Sep 12 '22 at 23:28