2016-07-29 76 views
3

我在部署本地基于virtualbox的群集时遇到问题 - 我按照官方docker文档中有关使用docker-machine工具设置master/worker节点的说明。我在dockerhub上创建了令牌,并且使用--swarm(和--swarm-master)和--warm-discovery令牌:// XXXX ...迄今为止非常好,两台机器运行,似乎已注册为Swarm master,工人:使用docker-machine进行安装Swarm

[email protected]:~$ docker-machine ls 
NAME   ACTIVE  DRIVER  STATE  URL       SWARM     DOCKER ERRORS 
swarm-master * (swarm) virtualbox Running tcp://192.168.99.100:2376 swarm-master (master) v1.12.0 
swarm-node1 -   virtualbox Running tcp://192.168.99.101:2376 swarm-master   v1.12.0 
[email protected]:~$ docker run --rm swarm list token://[....] 
192.168.99.101:2376 
192.168.99.100:2376 

和设置使用“的eval $(泊坞窗机ENV --swarm群主)”正确的环境价值观后,我可以使用“泊坞窗信息”,说明我有两个节点的状态运行... 但任何尝试运行任何其他码头群swarm命令(码头节点...,码头服务...)我得到“错误响应守护进程:404页未找到”。

我在做什么错?

回答

8

看起来您正在尝试使用新的swarm mode功能与较旧的docker swarm相比较。

下面的脚本创建了3名管理者和工人2(使用泊坞窗1.12.0)一个HA集群群:

#========================= 
# Creating cluster members 
#========================= 
docker-machine create --driver virtualbox node1 
docker-machine create --driver virtualbox node2 
docker-machine create --driver virtualbox node3 
docker-machine create --driver virtualbox node4 
docker-machine create --driver virtualbox node5 

#=============== 
# Starting swarm 
#=============== 
MANAGER_IP=$(docker-machine ip node1) 

docker-machine ssh node1 docker swarm init --advertise-addr $MANAGER_IP 

#=============== 
# Adding members 
#=============== 
MANAGER_TOKEN=$(docker-machine ssh node1 docker swarm join-token --quiet manager) 
WORKER_TOKEN=$(docker-machine ssh node1 docker swarm join-token --quiet worker) 

docker-machine ssh node2 docker swarm join --token $MANAGER_TOKEN $MANAGER_IP:2377 
docker-machine ssh node3 docker swarm join --token $MANAGER_TOKEN $MANAGER_IP:2377 
docker-machine ssh node4 docker swarm join --token $WORKER_TOKEN $MANAGER_IP:2377 
docker-machine ssh node5 docker swarm join --token $WORKER_TOKEN $MANAGER_IP:2377 

列表中的群组成员

$ docker-machine ssh node1 docker node ls 
ID       HOSTNAME STATUS AVAILABILITY MANAGER STATUS 
4s0mrh2u4sa2p260ung8ipb0m * node1  Ready Active  Leader 
5ra7b8cwarpcpa47p2gq2ecxs node2  Ready Active  Reachable 
66t3pq66ynlvyl3do6lpn9kzb node3  Ready Active   
7k5n1id2q6yncqjbv7l8ec0r5 node5  Ready Active   
833e4ya58hq62epplreyvwtnm node4  Ready Active 

创建服务

$ docker-machine ssh node1 docker service create --name web --replicas=10 -p 30000:80 nginx 

$ docker-machine ssh node1 docker service ps web 
ID       NAME IMAGE NODE DESIRED STATE CURRENT STATE   ERROR 
2fxy4n57p8ot3mn0kws96pnuk web.1 nginx node1 Running  Running 30 seconds ago 
cmm1s3h8ds7tmppf7pwvl5zxw web.2 nginx node5 Running  Running 6 seconds ago 
7ixgtqlz049ggi90363js088b web.3 nginx node1 Running  Running 30 seconds ago 
4o1e2wkh0x4rp8h9o73as8drf web.4 nginx node3 Running  Running 22 seconds ago 
6lufnzzddljlw0lnu0qyftzh6 web.5 nginx node3 Running  Running 22 seconds ago 
49g43g23t4r9lpmitfs4uu1j6 web.6 nginx node2 Running  Running 3 seconds ago 
43dopngi08licw4xttipnfdb6 web.7 nginx node2 Running  Running 3 seconds ago 
8d47dvmokf65xb271fyk3jlbu web.8 nginx node4 Running  Running 7 seconds ago 
2t56edm3k4x98yjkvgamyq6v4 web.9 nginx node5 Running  Running 6 seconds ago 
byij5j5pom1t3elu2ydteasg7 web.10 nginx node4 Running  Running 7 seconds ago 
+0

aha ...好吧,我可以这样编写脚本(或手动执行swarm init/join步骤),但我认为docker-machine --swarm *组选项应该为我自动设置swarm,至少docker-machine docs使它看起来如此...所以这些实际上无法与新的docker engine 1.12一起使用? –

+0

@JiříNovákDocker swarm已经集成到版本1.12的Docker引擎中。这是为了取代旧的Swarm,它作为容器运行。码头机器中的群体选项旨在使旧群体更易于使用。仍然可以使用它们,但是不能指望新的docker引擎命令(如“docker node”或“docker service”)正常工作。 –

+0

@ mark-oconnor对,我被群体的两个版本弄糊涂了,我发现它有更多的搜索和阅读后,我有几个小时的睡眠:)谢谢澄清... –

相关问题