# Private Registry image pulling fails **URL:** \ **Category:** SUSE Rancher Prime\ **Created:** [July 1, 2019, 2:04pm UTC](https://forums.suse.com/t/private-registry-image-pulling-fails/14685 "2019-07-01T14:04:14Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![vinothkumar.l](https://avatars.discourse-cdn.com/v4/letter/v/ee59a6/32.png) [@vinothkumar.l](https://forums.suse.com/u/vinothkumar.l)\ **Post date:** [July 1, 2019, 2:04pm UTC](https://forums.suse.com/t/private-registry-image-pulling-fails/14685/1 "2019-07-01T14:04:14Z")
Hi , I have deployed Rancher 2.2 and i am using private registry (Harbor). I am trying to build a RKE cluster via rancher UI. But the images are not getting pulled on the cluster nodes. It says the below: \*Error response from daemon: pull access denied , repository does not exist or may require 'docker login` But i have that particular repository in use and also i am able to pull those images manually from the respective nodes accessing the same repository. It fails only through the UI. Also I have set the harbor registry in Rancher’s global settings and still fails. Kindly assist. Thanks & Regards, Vino ---
**Author:** ![vinothkumar.l](https://avatars.discourse-cdn.com/v4/letter/v/ee59a6/32.png) [@vinothkumar.l](https://forums.suse.com/u/vinothkumar.l)\ **Post date:** [July 3, 2019, 5:18pm UTC](https://forums.suse.com/t/private-registry-image-pulling-fails/14685/2 "2019-07-03T17:18:08Z")
someone kindly help. ---
**Author:** ![teamktown](https://avatars.discourse-cdn.com/v4/letter/t/9e8a1a/32.png) [@teamktown](https://forums.suse.com/u/teamktown)\ **Post date:** [July 4, 2019, 11:32am UTC](https://forums.suse.com/t/private-registry-image-pulling-fails/14685/3 "2019-07-04T11:32:13Z")
Same here. I suspect that the reachability of the registry from the nodes is the critical factor. Even if pingable my money is on the fact that Harbor registry can be on port 443 and not 5000 I think that’s what is giving Rancher nodes pause for connectivity. Not sure of the path to resolution other than maybe running rancher with a private repo on startup. Guidance welcome as well to resolve this and may bump over to slack to see who’s done what. ---
**Author:** ![DineshC001](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/dineshc001/32/4629_2.png) [@DineshC001](https://forums.suse.com/u/DineshC001)\ **Post date:** [July 12, 2019, 2:51pm UTC](https://forums.suse.com/t/private-registry-image-pulling-fails/14685/4 "2019-07-12T14:51:58Z")
please paste the results of the below command: docker info ---
**Author:** ![vinothkumar.l](https://avatars.discourse-cdn.com/v4/letter/v/ee59a6/32.png) [@vinothkumar.l](https://forums.suse.com/u/vinothkumar.l)\ **Post date:** [July 17, 2019, 7:56am UTC](https://forums.suse.com/t/private-registry-image-pulling-fails/14685/5 "2019-07-17T07:56:57Z")
Hi Dinesh, Thanks for you response. Please find below the output Containers: 5 Running: 1 Paused: 0 Stopped: 4 Images: 2 Server Version: 18.09.2 Storage Driver: overlay2 Backing Filesystem: xfs Supports d\_type: true Native Overlay Diff: true Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: bridge host macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog Swarm: inactive Runtimes: runc Default Runtime: runc Init Binary: docker-init containerd version: bb71b10fd8f58240ca47fbb579b9d1028eea7c84 runc version: 2b18fe1d885ee5083ef9f0838fee39b62d653e30 init version: fec3683 Security Options: seccomp Profile: default Kernel Version: 3.10.0-693.17.1.el7.x86\_64 Operating System: CentOS Linux 7 (Core) OSType: linux Architecture: x86\_64 CPUs: 4 Total Memory: 15.51GiB Name: X.X.X.lan ID: 5IIJ:566G:E6CV:USMU:65KZ:MIOD:BAUZ:2DBU:DTSZ:SIRO:JN6H:A2DH Docker Root Dir: /var/lib/docker Debug Mode (client): false Debug Mode (server): false No Proxy: localhost,x.x.x.x,x.x.x.x.56,127.0.0.1,192.X.X.X,192.X.x.x,x.x.x.x.11,x.x.x.x.19,x.x.x.x.14,x.x.x.x.20,x.x.x.x.13,x.x.x.x.25,x.x.x.x.27,x.x.x.x.23,x.x.x.x.15,x.x.x.x.39,x.x.x.x.40,x.x.x.x.41,x.x.x.x.42,x.x.x.x.43,x.x.x.x.44,x.x.x.x.45,x.x.x.x.46,x.x.x.x.47,x.x.x.x.48,x.x.x.x.49,x.x.x.x.50,x.x.x.x.51,x.x.x.11,x.x.x.19,x.x.x.14,x.x.x.20,x.x.x.13,x.x.x.25,x.x.x.27,x.x.x.23,x.x.x.15,10.82.13.211,[dockersrv02.ad.X.com](http://dockersrv02.ad.X.com),dockersrv02,x.x.x.10,[ihthbreg.ad.X.com](http://ihthbreg.ad.X.com),ihthbreg,x.x.x.50,x.x.x.x.16,x.x.x.x.110,x.x.x.x.7,x.x.x.x.12,x.x.x.x.22,x.x.x.x.17,x.x.x.x.26,x.x.x.x.8,x.x.x.x.24,x.x.x.x.29,x.x.x.x.28,x.x.x.x.33,x.x.x.7,x.x.x.12,x.x.x.22,x.x.x.17,x.x.x.26,x.x.x.8,x.x.x.24,x.x.x.29,x.x.x.28,x.x.x.12,172.82.0.0/16,x.x.x.x.50,x.x.x.x.52,x.x.x.x.54,x.x.x.x.55,x.x.x.x.57,x.x.x.x.58,x.x.x.x.59 Labels: Experimental: false Insecure Registries: x.x.x.x 127.0.0.0/8 Live Restore Enabled: false Product License: Community Engine Thanks & Regards, Vinothkumar.L ---
**Author:** ![DineshC001](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/dineshc001/32/4629_2.png) [@DineshC001](https://forums.suse.com/u/DineshC001)\ **Post date:** [July 26, 2019, 9:44am UTC](https://forums.suse.com/t/private-registry-image-pulling-fails/14685/6 "2019-07-26T09:44:35Z")
Have you included ‘private\_registries’ within your rke cluster.yml. Also if it still does not work, try configuring a different port for the docker registry.