Question
Question
Failed to pull image from private repository on kubernetes cluster
Hello,
I’m using DO’s new kubernetes cluster and it seems there’s an issue pulling an image form a private repository. I am using GitLab on the cluster with a configured docker registry. The registry works and I can pull the image locally. However when deploying on kubernetes I get the following error:
“Failed to pull image {redacted}: rpc error: code = Unknown desc = Error response from daemon: Get {redacted}: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)”
From related issues online it appears most people get this error with a proxy/dns issue so could this be an internal DO issue?
The request is not even logged on the registry server so it does not appear to be an authentication issue either. (Although I have a dockercfg secret setup for authentication)
Thanks,
Ryan
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
×
I am also facing this issue. Is this something that you have figured out?
Haven’t investigated much more, just avoiding it for now. However their support directed me to a previous FAQ of someone managing to setup gitlab + private repository deploying before. Not much help but I will probably go over my deployment again.
Did you configure the imagePullSecrets in the deployment yaml?
https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
I’m having the exact same problem. I can pull images from any private docker registry outside of my cluster (eg dockerhub.io, gitlab.com etc). I can also push and pull images in private docker registries that I have created inside the kubernetes cluster (have created both a nexus registry and one using the ‘stable/docker-registry’ helm chart) from my local dev machine. The registries I have created in the cluster have a public https endpoint via a DigitalOcean load balancer.
I also discovered that if I SSH into the actual nodes themselves and use docker commands directly on underlying droplet I get exactly the same result (external registries work fine, internal fail). Any help appreciated. I don’t want to admit how much sweat I have wasted on this one.
I am also having the exact same problem.One of my node can pull image and 2 of them can’t. I built a private repo inside k8 cluster.
I had created secret with docker hub credentials and I was getting the same error. Then I added https:// and it started working for me.
kubectl create secret docker-registry [name] –docker-server=https://index.docker.io/v1/ –docker-username=[dockerUsername] –docker-password=[dockerToken] –docker-email=[emailassociatedwithDocker]