<p>I am trying to deploy a simple node.js application with the new Kubernetes support in Bluemix. When I run the container I made, I get a <code>ImagePullBackOff</code> error, which means it can't pull down the image. </p>

<p><div class="snippet" data-lang="js" data-hide="false" data-console="true" data-babel="false">
<div class="snippet-code">
<pre class="snippet-code-html lang-html prettyprint-override"><code>NAME                                  READY     STATUS             RESTARTS   AGE
hello-node-2399519400-6m8dz           0/1       ImagePullBackOff   0          13m</code></pre>
</div>
</div>
</p>

<p>My Docker image uses the node.js base image.</p>

<p><div class="snippet" data-lang="js" data-hide="false" data-console="true" data-babel="false">
<div class="snippet-code">
<pre class="snippet-code-html lang-html prettyprint-override"><code>FROM node:6.9.2
EXPOSE 8080
COPY server.js .
CMD node server.js</code></pre>
</div>
</div>
</p>

<p>I deployed using:</p>

<p><div class="snippet" data-lang="js" data-hide="false" data-console="true" data-babel="false">
<div class="snippet-code">
<pre class="snippet-code-html lang-html prettyprint-override"><code>docker build -t hello-node:v1 .
kubectl run hello-node --image=hello-node:v1 --port=8080</code></pre>
</div>
</div>
</p>

<p>I am thinking that Bluemix can't pull down the node.js image, but I am not certain. </p>

<p>I see the docker build of the image, and I'm presuming that you're using the kubectl with the exported cluster config (bx cs cluster-config ...), so that it's targetting your cluster.</p>

<p>Did you tag and push that image from your local docker into the bluemix registry, or to another remote registry that would be accessible from the container service?  (My apologies if this is obvious - just didn't see the step there to tag and push it to a registry that would be available).</p>
