Imported docker image doesn't run on kubernetes

[lppier]

Hi, 

I am setting up some servers in an offline environment, and am downloading some tensorflow images for use on these offline servers. 

The kubernetes cluster has been set up, and we have verified that the pods can be allocated to the various worker nodes. 

The issue now here is this - typically I use on the internet computer

docker save mycontainername >  myimage.tar 

and then on the offline server

docker load < myimage.tar 

For the most part this has worked when we run the pod on kubernetes. 

However, now we are trying to make commits to the container on the internet computer. 

So now, 

docker commit CONTAINER_ID mycontainername2

followed by: 

docker save mycontainername2 > myimage2.tar

on the offline server:

docker load < myimage2.tar

In this case, kubernetes fails to load the pod that launches the docker container. We keep seeing crashloop as soon as the pod is launched.  The difference is the container image in the second case had 1 commit. 

However, if I run mycontainername2 in nvidia-docker/docker on the offline machine, it works. 

What could be the issue here? Could someone versed in docker/kubernetes help us out here? 

Thanks. 

Pier. 

[Tim Hockin]

It could be that kubernetes is trying to re-pull the image. Did you
set `imagePullPolicy: Never` ?

On Mon, Oct 30, 2017 at 11:15 PM, lppier <mads...@gmail.com> wrote:
> Hi,
>
> I am setting up some servers in an offline environment, and am downloading
> some tensorflow images for use on these offline servers.
> The kubernetes cluster has been set up, and we have verified that the pods
> can be allocated to the various worker nodes.
>
> The issue now here is this - typically I use on the internet computer
>
> docker save mycontainername > myimage.tar
>
> and then on the offline server
>
> docker load < myimage.tar
>
> For the most part this has worked when we run the pod on kubernetes.
> However, now we are trying to make commits to the container on the internet
> computer.
> So now,
>
> docker commit CONTAINER_ID mycontainername2
>
> followed by:
>
> docker save mycontainername2 > myimage2.tar
>
> on the offline server:
>
> docker load < myimage2.tar
>
> In this case, kubernetes fails to load the pod that launches the docker
> container. We keep seeing crashloop as soon as the pod is launched. The
> difference is the container image in the second case had 1 commit.
>

> What could be the issue here? Could someone versed in docker/kubernetes help
> us out here?
>
> Thanks.
>
> Pier.
>

> --
> You received this message because you are subscribed to the Google Groups
> "Kubernetes user discussion and Q&A" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to kubernetes-use...@googlegroups.com.
> To post to this group, send email to kubernet...@googlegroups.com.
> Visit this group at https://groups.google.com/group/kubernetes-users.
> For more options, visit https://groups.google.com/d/optout.

[Pier Lim]

Yes I did ... sorry I forgot to mention that. I don't think it's the image because my image without commits is loaded just fine.

Thanks.

---

From: 'Tim Hockin' via Kubernetes user discussion and Q&A <kubernet...@googlegroups.com>
Sent: Wednesday, November 1, 2017 2:03:01 AM
To: Kubernetes user discussion and Q&A
Subject: Re: [kubernetes-users] Imported docker image doesn't run on kubernetes

 

You received this message because you are subscribed to a topic in the Google Groups "Kubernetes user discussion and Q&A" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/kubernetes-users/_rysXciIzms/unsubscribe.
To unsubscribe from this group and all its topics, send an email to kubernetes-use...@googlegroups.com.

[Tim Hockin]

You'll have to post more details then, including kubelet logs.