| |
| META TOPICPARENT |
name="CloudSuite" |
-- HamidMoghaddam - 18 May 2016 |
| |
- Got error "Cannot connect to the Docker daemon. Is the docker daemon running on this host?" so run sudo usermod -aG docker mike and sudo usermod -aG docker root then logout and login
- docker pull progrium/consul
- add DOCKER_OPTS="-H unix:///var/run/docker.sock -H tcp://0.0.0.0:2375 \ --cluster-store consul://10.0.100.62:8500 \ --cluster-advertise eth0:2375" to /etc/default/docker(in this link
 they wrote step 6 completly wrong and take one day to figure out what happens.)
|
|
<
< |
- sudo service docker restart
- docker run -d -p 8500:8500 --hostname 10.0.100.62 --name consul-store progrium/consul -server -bootstrap (again in the swarm installation guide by CloudSuite, they made this line mistake and consumed a lot of time to solve it)
- docker run -d --name swarm-agent swarm join --advertise=10.0.100.62 :2375 consul://10.0.100.62:8500 (again CloudSuite team writed this line wrongly. Now I am not surprised why CloudSuite is such a confusing software)
|
>
> |
- sudo service docker restart
- docker run -d -p 8500:8500 --hostname 10.0.100.62 --name consul-store progrium/consul -server -bootstrap (again in the swarm installation guide by CloudSuite, they made this line mistake and consumed a lot of time to solve it)
- docker run -d --name swarm-agent swarm join --advertise=10.0.100.62 :2375 consul://10.0.100.62:8500 (again CloudSuite team writed this line wrongly. Now I am not surprised why CloudSuite is such a confusing software)
|
| |
- repeat step 2,3,4,6,7,9 on every VMs but just in step 9 replace --advertise IP address with each VM IP address.
|
|
<
< |
- docker -H tcp://10.0.100.62:22222 network create --driver overlay swarm-network
|
>
> |
- docker -H tcp://10.0.100.62:22222 network create --driver overlay swarm-network
|
| | Frontend
I did following steps on frontend machine(Please check swarm-agent is running: docker start 'swarm-agent')
1. docker pull cloudsuite/web-serving:web_server |
|
<
< | 2. docker -H tcp://10.0.100.62:22222 run -dt --name=web_server cloudsuite/web-serving:web_server /etc/bootstrap.sh |
| | \ No newline at end of file |
|
>
> | 2. docker -H tcp://10.0.100.62:22222 run -dt --net swarm-agent --name=web_server cloudsuite/web-serving:web_server /etc/bootstrap.sh I got subnet conflict in this stage (Thanks again to CloudSuit team) After one they searching I found out creating overlay network (step 11 of swarm manager creation) should be change to docker -H tcp://10.0.100.62:22222 network create --driver overlay --subnet=172.28.0.0/16 --ip-range=172.28.5.0/24 swarm-network
Backend
- docker pull cloudsuite/web-serving:db_server
- docker run -dt --net=my_net --name=mysql_server cloudsuite/web-serving:db_server
Memcache
- docker pull cloudsuite/web-serving:memcached_server
- docker run -dt --net=my_net --name=memcache_server cloudsuite/web-serving:memcached_server
Client
- docker pull cloudsuite/web-serving:faban_client
- WEB_SERVER_IP=$(docker inspect --format '' web_server)
- docker run --net=my_net --name=faban_client cloudsuite/web-serving:faban_client WEB_SERVER_IP
|
Copyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.