Docker Community Forums

Share and learn in the Docker community.

Fail to install UCP 0.5 controller on CentOS 7.1


(Clarence Ho) #1

System setup:

  • OS: CentOS 7.1
  • Kernel: 4.3.0
  • Docker engine: 1.9.1
  • Network interfaces:
    • em1: 192.168.0.11 (this is the internal network interface)
    • em2: 202.181.203.21 (this is the public address that I want to setup UCP on)

Install command (UCP controller on the above host):

docker run --rm -it -v /var/run/docker.sock:/var/run/docker.sock --name ucp dockerorca/ucp install -i --host-address 202.181.203.21

Logs from console during installation:

INFO[0000] Verifying your system is compatible with UCP
Please choose your initial Orca admin password:
Confirm your initial password:
INFO[0005] Pulling required images
Please enter your Docker Hub username: skywideclarence
Please enter your Docker Hub password:
Please enter your Docker Hub e-mail address: clarence@skywidesoft.com
INFO[0024] Pulling required images
WARN[0115] None of the hostnames we’ll be using in the UCP certificates [compute1 127.0.0.1 172.17.0.1 202.181.203.21] contain a domain component. Your generated certs may fail TLS validation unless you only use one of these shortnames or IPs to connect. You can use the --san flag to add more aliases

You may enter additional aliases (SANs) now or press enter to proceed with the above list.
Additional aliases: ucp.skywidesoft.com
INFO[0138] Installing UCP with host address 202.181.203.21 - If this is incorrect, please use the ‘–host-address’ flag to specify a different address
INFO[0024] Generating Swarm Root CA
INFO[0041] Generating UCP Root CA
INFO[0052] Deploying UCP Containers
ERRO[0115] We were unable to communicate with proxy we just started at address 202.181.203.21. If this address is incorrect, re-run the install using the ‘–host-address’ option. Run “docker logs ucp-proxy” for more details from the proxy
FATA[0115] Unable to connect to system

Output from docker logs ucp-proxy

Listening on 2376
Using TLS

Output of docker ps -a

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
8c2340ad7057 dockerorca/ucp-proxy:latest “/bin/run” 9 minutes ago Up 9 minutes 0.0.0.0:12376->2376/tcp ucp-proxy
6b3b15e67247 dockerorca/ucp-etcd:2.2.0 “/bin/etcd --data-dir” 9 minutes ago Up 9 minutes 2380/tcp, 4001/tcp, 7001/tcp, 0.0.0.0:12380->12380/tcp, 0.0.0.0:12379->2379/tcp ucp-kv

Kindly advice
Clarence


(Banjot) #2

Output of docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
8c2340ad7057 dockerorca/ucp-proxy:latest “/bin/run” 9 minutes ago Up 9 minutes 0.0.0.0:12376->2376/tcp ucp-proxy
6b3b15e67247 dockerorca/ucp-etcd:2.2.0 “/bin/etcd --data-dir” 9 minutes ago Up 9 minutes 2380/tcp, 4001/tcp, 7001/tcp, 0.0.0.0:12380->12380/tcp, 0.0.0.0:12379->2379/tcp ucp-kv

this looks to be missing few other containers including:
ucp-controller
ucp-swarm-manager
ucp-swarm-join

you can try re-running the install with the options: --fresh-install and --debug. This might show you more detail about what’s happening when the controller, swarm-manager, and swarm-join. Based on your docker ps -a, it looks like they were never started.


(Clarence Ho) #3

I found that there are some issues within my docker engine startup options.

Previously I installed Docker Swarm, so my docker engine start option (stored in /usr/lib/systemd/system/docker.service) is something like below:
ExecStart=/usr/bin/docker daemon -H tcp://0.0.0.0:2375 -H unix:///var/run/docker.sock --cluster-store=...

On the other hand, I found a problem on starting the containers.

As a result, I change the line to the below one:
ExecStart=/usr/bin/docker daemon -H tcp://0.0.0.0:2375 -H unix:///var/run/docker.sock --exec-opt native.cgroupdriver=cgroupfs

Then I started a fresh installation and UCP controller was installed successfully.

Regards
Clarence


(Banjot) #4

great to hear you got it working! We’ll try to catch this in the docs or on the ucp bootstrap process.