-
-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pods stuck on ImagePullBackOff status #329
Comments
@timfallmk any ideas why the image hash doesn't exist? |
I was afraid of this. It's probably because of my messing with release process. I'll push that tag again manually. |
@grampelberg Looks like I was wrong, the image appears to exist: https://hub.docker.com/layers/ksync/ksync/git-a5628b9/images/sha256-fcb07b0634571432d76736b695c676365907b4215d2f0edd179a6ef2df2fa486 @kollender Can you try again and see if it's a transient error? |
@timfallmk again :\
And the image in the deamonset is |
What's in the logs? |
@grampelberg what is the command for that? |
Honestly it sounds like you've got connectivity issues to docker hub. Can you run any other images like alpine? |
Here are some logs:
|
Yup, looks like you've got issues pulling the image, not much we can do to help out with that I'm afraid =/ |
Yeah, seems like that. |
After ksync installation, tried to run
ksync init
and got:When I run
ksync doctor
I get:The output of
ksync version
:All of the pods are in the same status (
kubectl --namespace=kube-system --context= get pods -lapp=ksync
):The image in the DS is
ksync/ksync:git-a5628b9
.The K8s cluster is a GKE cluster, and this is the output of
kubectl version
:The text was updated successfully, but these errors were encountered: