Hi all,
I’m a newcomer, but I meet this problem for several days. I’ve followed the official quick start guide:
[root@localhost Desktop]# sudo docker run -d --restart=always -p 8080:8080 rancher/server fb80a348912cc8356a4de7f59c0c5725f26ed919a085031d6c57e00517940e07
and the rancher server was started, also I can access the rancher UI by http://172.16.0.12:8080
next I followed the command provided by rancher UI:
[root@localhost Desktop]# sudo docker run -e CATTLE_AGENT_IP="172.16.0.12" -d --privileged -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/rancher:/var/lib/rancher rancher/agent http://172.16.0.12:8080/v1/scripts/E82B9FC35536F6B156BD:1466611200000:EM4SAU2CKzNfumVOSO1K3CvVTps 2944733896e85c63f6d37e51179a1f4ba9d7b7da99ab653a619e6743ab452f72
after that, I didn’t see any host shown in rancher UI, but both server and agent container are started:
[root@localhost Desktop]# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 2944733896e8 rancher/agent "/run.sh http://172.1" 6 minutes ago Up 6 minutes goofy_boyd fb80a348912c rancher/server "/usr/bin/s6-svscan /" 9 minutes ago Up 9 minutes 3306/tcp, 0.0.0.0:8080->8080/tcp fervent_hawking
Am I wrong at any steps of this guide ?
BTW, I ran CentOS 7(kernel 3.10.0) on Vmware and both server and agent are on the same OS.
Thanks
Jiebo