-
Notifications
You must be signed in to change notification settings - Fork 116
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
Failed to pull zookeeper image from private registry #621
Comments
Sorry for the late response here. When you do this, and look at the |
No worries, thanks for looking into it. `david@ubuntu:~$ kubectl describe pod example-solrcloud-zookeeper-0 Normal Scheduled 23s default-scheduler Successfully assigned local-dev/example-solrcloud-zookeeper-0 to sstaul-22005 ` |
Hi there @davidl789, did you manage to solve this issue? Currently facing the same problem... |
Installed the apache/solr helm chart and override to pull the zookeeper image from our private registry with the command below:
helm install example apache-solr/solr --version 0.7.1 --set zk.provided.image.repository=my-registry.com.au/myuser/my_solrzookeeper --set zk.provided.image.tag=0.1.379 --set zk.provided.image.imagePullSecret=my-docker-registry-key
It failed to pull the zookeeper image from our private registry with error "no basic auth credentials" :
" Warning Failed 10s kubelet Failed to pull image "my-registry.sandstone.com.au/myuser/my_solrzookeeper:0.1.379": rpc error: code = Unknown desc = Error response from daemon: Head "https://my-registry.sandstone.com.au/v2/myuser/my_solrzookeeper/manifests/0.1.379": no basic auth credentials"
It appears the provided pull secret "my-docker-registry-key" is ignored and not sent to the private registry.
However, the solrcloud image can be pulled successfully from our private registry with the command below using the same pull secret:
helm install example apache-solr/solr --version 0.7.1 --set image.repository=my-registry.sandstone.com.au/myuser/my_solrcloud --set image.tag=0.1.3464 --set image.imagePullSecret=my-docker-registry-key
The text was updated successfully, but these errors were encountered: