Zero-to-jupyterhub-k8s: "Init:ImagePullBackOff", "FailedSync", "Error syncing pod" issues when building from a newly-created Docker image on Google Cloud

[UsDAnDreS]

Contents of config.yaml

proxy:
  secretToken: ...
singleuser:
  image:
    name: gcr.io/uh-dsi-workshop-206823/workshop1
    tag: b92c23c

I was able to use repo2docker in order to create an image, and pushed it to Google Cloud:

Then I inserted the image name and tag into the 'config.yaml' file (as can be seen above), ran a helm upgrade,

but it failed and showed "Init : ImagePullBackOff" all around

I also tried to "diagnose" those pods, but I was probably doing it wrong..

Anyone know why upgrading Helm with this image info didn't quite work out? What might be the reason behind those "ImagePullBackOff"s?

Thanks in advance!

[UsDAnDreS]

Attached is a diagnostic to on of the failed pods (it's the same "Event" for all three of them: FailedSync, Error syncing pod")

[choldgraf]

hmmm, does kubectl logs show anything from the broken prepullers?

[UsDAnDreS]

@choldgraf The issue has been taken care of by me using Google Cloud console instead of the local machine. As that's where the Image was pushed to (Google Cloud), so I feel like that might've been it, but can't be sure of anything at that point.

[choldgraf]

cool - thanks for following up!