Docker Community Forums

Share and learn in the Docker community.

Unable to re-install DTR : "Bind for 0.0.0.0:444 failed: port is already allocated" (on new instal)

ucp
dtr

(Fimm) #1

Hi,

I installed DTR & Docker UCP on the same VM, using port 443 for UCP and 444 for DTR.

My issue is I couldn’t login form docker engine to DTR, getting error 404 while everything was nicely up and running…

So I assumed it was port related and I tried changing theses with docker run -p, but couldn’t restart UCP-controler nor DTR load balancer.

So I removed everything and installed Docker UCP with port 444 as an install option (since it cannot be changed afterwards).
Got UCP to run nicely but then when I installed DTR again using (as root)
# bash -c "$(sudo docker run docker/trusted-registry install)
I get this error :
docker.errors.APIError: 500 Server Error: Internal Server Error ("failed to create endpoint docker_trusted_registry_load_balancer on network dtr: Bind for 0.0.0.0:444 failed: port is already allocated")
which is really wired, because the default port is 443.

So I deleted every images and containers from DTR, and also any volumes that were not in use, but still get the same problem…

Is there any way I could specify DTR listening port during install, or remove this from previous configuration that is obviously hanging around…

I’m gonna try to remove UCP and install DTR only and see…

Thank you for your help.


docker ps: CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 70ed7303053a docker/trusted-registry-index:1.4.3 "server" 22 minutes ago Up 22 minutes docker_trusted_registry_registry_index cbbee0a9f2cf docker/trusted-registry-distribution:v2.2.1 "registry /config/sto" 22 minutes ago Restarting (2) 9 minutes ago 5000/tcp docker_trusted_registry_image_storage_1 f2284af1313f docker/trusted-registry-distribution:v2.2.1 "registry /config/sto" 22 minutes ago Restarting (2) 9 minutes ago 5000/tcp docker_trusted_registry_image_storage_0 1e26fbd9916f postgres:9.4.1 "/docker-entrypoint.s" 22 minutes ago Up 22 minutes 5432/tcp docker_trusted_registry_postgres a2fcadde590c docker/ucp-controller:1.0.0 "/bin/controller serv" 59 minutes ago Up 59 minutes 0.0.0.0:444->8080/tcp ucp-controller d59c46cad6c5 docker/ucp-cfssl:1.0.0 "/bin/cfssl serve -ad" 59 minutes ago Up 59 minutes 8888/tcp, 0.0.0.0:12381->12381/tcp ucp-cluster-root-ca a9c3d9764a9d docker/ucp-cfssl:1.0.0 "/bin/cfssl serve -ad" 59 minutes ago Up 59 minutes 8888/tcp, 0.0.0.0:12382->12382/tcp ucp-client-root-ca 804160eb5386 docker/ucp-swarm:1.0.0 "/swarm manage --tlsv" 59 minutes ago Up 59 minutes 0.0.0.0:2376->2375/tcp ucp-swarm-manager 5a3416884b7b docker/ucp-swarm:1.0.0 "/swarm join --discov" 59 minutes ago Up 59 minutes 2375/tcp ucp-swarm-join 65fd0ccfd81d docker/ucp-proxy:1.0.0 "/bin/run" 59 minutes ago Up 59 minutes 0.0.0.0:12376->2376/tcp ucp-proxy 53d02eb20b2d docker/ucp-etcd:1.0.0 "/bin/etcd --data-dir" 59 minutes ago Up 59 minutes 2380/tcp, 4001/tcp, 7001/tcp, 0.0.0.0:12380->12380/tcp, 0.0.0.0:12379->2379/tcp ucp-kv

So yes port 444 is in use, which is what is expected, what is not normal is that DTR want to listen on port 444 which should not be the default behaviour.


(Fimm) #2

Solved.

Deleted and re-installed everything.
However DTR configuration was still there, even though I erased everything I could find…