Docker Community Forums

Share and learn in the Docker community.

DTR installation issue in UCP

docker

(Bobinjosek) #1

Hi Team,

I am trying to install UCP in RHEL 7.2 UCP installation went well.But DTR installation is failed with below error…Though We have disabled firewall and Selinux in UCP and DTR server.Even we have tried to use --replica-http-port and --replica-https-port and got the same error message

[root@test4 ~]# docker run -it --rm docker/dtr install --ucp-url https://10.126.40.227 --ucp-node test4 --dtr-external-url 10.126.40.243 --ucp-username admin --ucp-password xxxxxx --ucp-ca "$(cat ucp-ca.pem)"
INFO[0000] Beginning Docker Trusted Registry installation
INFO[0000] Validating UCP cert
INFO[0000] UCP cert validation successful
ERRO[0001] Make sure that there is a node in your UCP cluster where port 80 and port 443 are open. Also confirm that all UCP node have the DTR images or can obtain them from Docker Hub.
FATA[0001] Problem running container ‘dtr-phase2’ from image ‘docker/dtr:2.0.2’: Couldn’t create container ‘dtr-phase2’ from image ‘docker/dtr:2.0.2’: Error response from daemon: Unable to find a node that satisfies the following conditions

Please help us to resolve the issue,

Thanks
Bobin


(Vivek Saraswat) #2

Hi bobin,

I see the following error: “ERRO[0001] Make sure that there is a node in your UCP cluster where port 80 and port 443 are open. Also confirm that all UCP node have the DTR images or can obtain them from Docker Hub.”

Are you trying to install the DTR replica on the same node as a current UCP controller? Both UCP and DTR use ports 80/443.

If this is in fact the issue, the way around this is to either:

  1. Install DTR on a node joined to UCP cluster but is not itself a UCP controller
  2. Install DTR with different ports. When using docker/dtr install command you can specify --replica-http-port and --replica-https-port as shown in the DTR Reference Guide. If you are running an HA setup make sure the load balancer knows to use the alternative ports.
  3. Install UCP with different ports (so that DTR can use 80/443). This can be done when doing docker/ucp install or docker/ucp join --replica by specifying --controller-port as shown in the UCP Reference Guide.

(Jaydipta) #3

Able to login to DTR web UI.
But when I try to “docker login my-host-name” ,
it expects ID and Pwd. Once I give it correctly it throws
an error :- “Error response from daemon: Get https://my-host-name/v1/users/: Service Unavailable”

Please let me know how ro fix this?


(Bobinjosek) #4

Thanks Vivek for the response…

I was trying to install the DTR on different RHEL 7.2 servers.I could resolve the port and overlay network issue.

Thanks,
Bobin


(Frankgrecojr) #5

I am encountering the same issue. I am using your first option:

docker run -it --rm
docker/dtr install
–ucp-url https://10.240.243.223:443
–ucp-node 10.240.243.150
–dtr-external-url https://10.240.243.150:443
–ucp-username “admin” --ucp-password “orca”
–ucp-ca “$(cat ucp-ca.pem)” \

where 10.240.243.223 is one of my controller nodes and 10.240.243.150 is a not in the ucp cluster but is not a ucp controller node.

I am getting the following error:

INFO[0000] Beginning Docker Trusted Registry installation
INFO[0000] Validating UCP cert
INFO[0000] UCP cert validation successful
ERRO[0000] Make sure that there is a node in your UCP cluster where port 80 and port 443 are open. Also confirm that all UCP node have the DTR images or can obtain them from Docker Hub.
FATA[0000] Problem running container ‘dtr-phase2’ from image ‘docker/dtr:2.0.3’: Couldn’t create container ‘dtr-phase2’ from image ‘docker/dtr:2.0.3’: Error response from daemon: Unable to find a node that satisfies the following conditions
[available container slots]
[node==10.240.243.150 node!=ip-10-240-243-223.ec2.internal node!=ip-10-240-243-10.ec2.internal node!=ip-10-240-243-160.ec2.internal]

I’m confused as to why it is saying (on the last line) that the node has to be one of my 3 controller nodes when that contradicts what your (1) suggestion was.


(Azeratul) #6

Hi, could you please let me know how you fixed the issue, I am also completely stuck with this one?


(Sérgio Pelissari) #7

You trying to install it on a reserved node or it already the reserved server for registry? If you are using the same server check for conflict on port 443 used by controller and replica.