<p>Some times I observe Imagepullbackoff or Imagepullerror in kubernets deployment.
Is there any restriction for docker image size on kubernetes for pulling image.</p>
<p>Thanks</p>

Khumar
<p>It's straightforward to get a ~1 GB image (anything that <code>apt-get install build-essential</code> will clock in in the hundreds of megabytes easily), and the Kubernetes clusters I use day-to-day handle that just fine.</p>

<p>In the past I've had trouble with Docker with single layers in the 1 GB+ range, and whole images in the 5 GB+ range.  These have generally manifested as problems with <code>docker push</code> and <code>docker pull</code> being unreliable, and those in turn could correspond to the Kubernetes errors you're seeing.</p>

<p>As a general rule, if you're building containers by taking a language runtime and adding your application on top of it, and you're not trying to bundle any especially large data set into your container, you're probably fine, even if you're being inefficient about how you build it.</p>

<p>(Alpine isn't a silver bullet here: you might save ~150 MB over an Ubuntu base image, but if you're still installing a full C toolchain and adding a big dataset into the image proper, you'll easily get up into the problematic range.  A ~200-300 MB Ubuntu-based container will work just fine and won't cause any operational problems beyond the time and space required to pull it.)</p>
