Why am I suddenly getting ImagePullPolicy errors?

7/14/2018

Using GKE

Trying to deploy a yml that has a docker image that contains gcr.io/myproject-101/pyftp. I have not had a problem with pulling this image at all until just recently. And from the looks of it it just started happening after my trial ran out. I've tried recreating my cluster and directly getting the path from the container registry.

Back-off pulling image "gcr.io/myproject-101/pyftp" BackOff Jul 14, 2018, 3:49:29 AM    Jul 14, 2018, 3:59:27 AM    41
Failed to pull image "gcr.io/myproject-101/pyftp": rpc error: code = Unknown desc = error pulling image configuration: unknown blob Failed  Jul 14, 2018, 3:49:28 AM    Jul 14, 2018, 3:51:02 AM    4

I keep reading that it has to due with coming from private repos...but nothing has changed. They're all within my one project. Pull have worked before. Only thing that I can think of that I have done recently is start to make use of "cookies" since I had to to hook my github desktop application into the private repo. To do this I was linked to a page that provided me commands to run to push to that repo. Does that have something to do with it?

-- quantomworks
google-container-registry
google-kubernetes-engine
kubernetes

1 Answer

7/17/2018

Using default settings, builds are required to be tagged as latest. Using default auto-build settings for container builder, it lets the tag as the commit's hash rather than the latest tag.

-- quantomworks
Source: StackOverflow