Docker Swarm集群搭建与测试

最新推荐文章于 2024-04-22 15:58:24 发布
最新推荐文章于 2024-04-22 15:58:24 发布
阅读量962 收藏
点赞数
分类专栏： 容器 文章标签： docker 容器 运维
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/HAI7XIAO/article/details/122650287
版权

Docker Swarm

文档

https://docs.docker.com/engine/swarm/

参考

https://qiita.com/Brutus/items/b3dfe5957294caa82669

https://docs.docker.jp/swarm/overview.html

架构示意

Manager可以管理集群，也可以运行容器

worker只能运行容器

在这里插入图片描述

搭建

docker环境搭建

OS设置

# 关闭SELinux，firewalld

# 网络设置
[root@vm1 ~]# ip -br a | grep 0s8 | awk '{print $3}'
192.168.50.100/24

[root@vm2 ~]# ip -br a | grep 0s8 | awk '{print $3}'
192.168.50.120/24

安装docker，compose

# docker
[root@vm1 ~]# cat install-docker.sh
yum remove docker* -y
rm -rf /var/lib/docker
yum -y install wget
wget -O /etc/yum.repos.d/docker-ce.repo https://download.docker.com/linux/centos/docker-ce.repo
yum install docker-ce docker-ce-cli containerd.io -y
docker --version
systemctl enable docker --now
docker run hello-world
[root@vm1 ~]# bash install-docker.sh

# 安装docker-compose（任意）
[root@vm1 ~]# curl -L "https://github.com/docker/compose/releases/download/1.29.2/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
[root@vm1 ~]# chmod +x /usr/local/bin/docker-compose

[root@vm1 ~]# docker -v
Docker version 20.10.12, build e91ed57

[root@vm1 ~]# docker-compose -v
docker-compose version 1.29.2, build 5becea4c

[root@vm2 ~]# docker -v
Docker version 20.10.12, build e91ed57

[root@vm2 ~]# docker-compose -v
docker-compose version 1.29.2, build 5becea4c

docker0网络（不用修改）

[root@vm1 ~]# docker network inspect bridge -f "{{.IPAM.Config}}"
[{192.168.80.0/24  192.168.80.1 map[]}]

[root@vm2 ~]# docker network inspect bridge -f "{{.IPAM.Config}}"
[{192.168.90.0/24  192.168.90.1 map[]}]

Swarm集群搭建

初始化#1（manager）

[root@vm1 ~]# docker swarm init --advertise-addr 192.168.50.100
Swarm initialized: current node (kdcrkd6sqteevq9jgy70fd0h0) is now a manager.

To add a worker to this swarm, run the following command:

    docker swarm join --token SWMTKN-1-0h1lwim8eh8ygwmh9mg3chuep8lf3dh0z8iv79v3km7itl28ww-4yt8thj4v7a2sj45iab6v8qqj 192.168.50.100:2377

To add a manager to this swarm, run 'docker swarm join-token manager' and follow the instructions.

# 亦可手动获取令牌token

[root@vm1 ~]# docker swarm join-token worker
To add a worker to this swarm, run the following command:

    docker swarm join --token SWMTKN-1-0h1lwim8eh8ygwmh9mg3chuep8lf3dh0z8iv79v3km7itl28ww-4yt8thj4v7a2sj45iab6v8qqj 192.168.50.100:2377

# 查看集群节点

[root@vm1 ~]# docker node ls
ID                            HOSTNAME   STATUS    AVAILABILITY   MANAGER STATUS   ENGINE VERSION
kdcrkd6sqteevq9jgy70fd0h0 *   vm1        Ready     Active         Leader           20.10.12

worker加入集群

[root@vm2 ~]# docker swarm join --token SWMTKN-1-0h1lwim8eh8ygwmh9mg3chuep8lf3dh0z8iv79v3km7itl28ww-4yt8thj4v7a2sj45iab6v8qqj 192.168.50.100:2377
This node joined a swarm as a worker.

查看集群节点

[root@vm2 ~]# docker node ls
Error response from daemon: This node is not a swarm manager. Worker nodes can't be used to view or modify cluster state. Please run this command on a manager node or promote the current node to a manager.

ID                            HOSTNAME   STATUS    AVAILABILITY   MANAGER STATUS   ENGINE VERSION
kdcrkd6sqteevq9jgy70fd0h0 *   vm1        Ready     Active         Leader           20.10.12
4hh92oj2meotbi0etnje15bzq     vm2        Ready     Active                          20.10.12

添加label

dns主机别名？

[root@vm1 ~]# docker node update --label-add name=swarm-master-1 vm1
vm1

[root@vm1 ~]# docker node update --label-add name=swarm-master-2 vm2
vm2

[root@vm1 ~]# docker node ls
ID                            HOSTNAME   STATUS    AVAILABILITY   MANAGER STATUS   ENGINE VERSION
kdcrkd6sqteevq9jgy70fd0h0 *   vm1        Ready     Active         Leader           20.10.12
4hh92oj2meotbi0etnje15bzq     vm2        Ready     Active                          20.10.12

查看label

[root@vm1 ~]# docker node inspect vm1 -f "{{.Spec.Labels}}"
map[name:swarm-master-1]

[root@vm1 ~]# docker node inspect vm2 -f "{{.Spec.Labels}}"
map[HOSTNAME:master-2 name:master-2]

这个label貌似没用？

[root@vm1 ~]# docker node update --help
Usage:  docker node update [OPTIONS] NODE
Update a node
Options:
      --availability string   Availability of the node ("active"|"pause"|"drain")
      --label-add list        Add or update a node label (key=value)
      --label-rm list         Remove a node label if exists
      --role string           Role of the node ("worker"|"manager")

[root@vm1 ~]# docker node update --label-add name=master-2 vm2
vm2
[root@vm1 ~]# echo $?
0
[root@vm1 ~]#

[root@vm1 ~]# docker node ls
ID                            HOSTNAME   STATUS    AVAILABILITY   MANAGER STATUS   ENGINE VERSION
kdcrkd6sqteevq9jgy70fd0h0 *   vm1        Ready     Active         Leader           20.10.12
4hh92oj2meotbi0etnje15bzq     vm2        Ready     Active                          20.10.12

[root@vm1 ~]# docker node promote master-2
Error: No such node: master-2

[root@vm1 ~]# docker node promote master-2
Error: No such node: master-2
[root@vm1 ~]# docker node update --label-add HOSTNAME=master-2 vm2
vm2
[root@vm1 ~]# docker node ls
ID                            HOSTNAME   STATUS    AVAILABILITY   MANAGER STATUS   ENGINE VERSION
kdcrkd6sqteevq9jgy70fd0h0 *   vm1        Ready     Active         Leader           20.10.12
4hh92oj2meotbi0etnje15bzq     vm2        Ready     Active                          20.10.12
[root@vm1 ~]# docker node promote master-2
Error: No such node: master-2

提升worker为master

[root@vm1 ~]# docker node ls
ID                            HOSTNAME   STATUS    AVAILABILITY   MANAGER STATUS   ENGINE VERSION
kdcrkd6sqteevq9jgy70fd0h0 *   vm1        Ready     Active         Leader           20.10.12
4hh92oj2meotbi0etnje15bzq     vm2        Ready     Active         Reachable        20.10.12

2号可以查看集群情况了

[root@vm2 ~]# docker node ls
ID                            HOSTNAME   STATUS    AVAILABILITY   MANAGER STATUS   ENGINE VERSION
kdcrkd6sqteevq9jgy70fd0h0     vm1        Ready     Active         Leader           20.10.12
4hh92oj2meotbi0etnje15bzq *   vm2        Ready     Active         Reachable        20.10.12

查看节点的信息

[root@vm1 ~]# docker node inspect vm2 -f "{{.Spec.Labels}}"
map[HOSTNAME:master-2 name:master-2]
[root@vm1 ~]# docker node inspect vm2

创建网络

指定为overlay

[root@vm1 ~]# docker network create -d overlay --subnet=192.168.82.0/24 --gateway=192.168.82.1 --attachable swarm-net
xywzrf7ftwenaxbu0zmewh183

查看

[root@vm1 ~]# docker network inspect swarm-net -f "{{.IPAM}}"
{default map[] [{192.168.82.0/24  192.168.82.1 map[]}]}

创建service并验证

创建

[root@vm1 ~]# docker service create --replicas 3 -p 10080:80 --network swarm-net --name nginx-cluster nginx
r4v6w094yxl370bynyzghh37a
overall progress: 3 out of 3 tasks
1/3: running   [==================================================>]
2/3: running   [==================================================>]
3/3: running   [==================================================>]
verify: Service converged
[root@vm1 ~]#

查看

[root@vm1 ~]# docker service ls
ID             NAME            MODE         REPLICAS   IMAGE          PORTS
r4v6w094yxl3   nginx-cluster   replicated   3/3        nginx:latest   *:10080->80/tcp

[root@vm1 ~]# ss -ntl | grep 10080
LISTEN 0      128                *:10080            *:*

[root@vm1 ~]# docker ps
CONTAINER ID   IMAGE          COMMAND                  CREATED         STATUS         PORTS     NAMES
3ddd0e479de6   nginx:latest   "/docker-entrypoint.…"   7 minutes ago   Up 7 minutes   80/tcp    nginx-cluster.1.6i1ncpnncxzxmsckwyahj9f7l

[root@vm1 ~]# docker port nginx-cluster.1.6i1ncpnncxzxmsckwyahj9f7l
[root@vm1 ~]# echo $?
0
[root@vm1 ~]#

访问

[root@vm1 ~]# curl 192.168.50.100:10080
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
...

在2号机上

[root@vm2 ~]# docker service  ls
ID             NAME            MODE         REPLICAS   IMAGE          PORTS
r4v6w094yxl3   nginx-cluster   replicated   3/3        nginx:latest   *:10080->80/tcp
[root@vm2 ~]# ss -ntl
State         Recv-Q        Send-Q               Local Address:Port                Peer Address:Port        Process
LISTEN        0             128                        0.0.0.0:22                       0.0.0.0:*
LISTEN        0             128                              *:10080                          *:*
LISTEN        0             128                              *:2377                           *:*
LISTEN        0             128                              *:7946                           *:*
LISTEN        0             128                           [::]:22                          [::]:*


[root@vm2 ~]# docker ps
CONTAINER ID   IMAGE          COMMAND                  CREATED         STATUS         PORTS     NAMES
6b1e246bdc34   nginx:latest   "/docker-entrypoint.…"   8 minutes ago   Up 8 minutes   80/tcp    nginx-cluster.3.yofvioldzci3k4geve7lykyrs
0d6709372322   nginx:latest   "/docker-entrypoint.…"   8 minutes ago   Up 8 minutes   80/tcp    nginx-cluster.2.gp7szi6348r0gfakr6v1i42ga
[root@vm2 ~]#

# 另一个容器在1号机上运行
[root@vm1 ~]# docker ps
CONTAINER ID   IMAGE          COMMAND                  CREATED         STATUS         PORTS     NAMES
3ddd0e479de6   nginx:latest   "/docker-entrypoint.…"   9 minutes ago   Up 9 minutes   80/tcp    nginx-cluster.1.6i1ncpnncxzxmsckwyahj9f7l

2号上也能看到overlay网络

[root@vm2 ~]# docker network ls | grep swarm-net
xywzrf7ftwen   swarm-net         overlay   swarm

访问2号机ip，看看转发

[root@vm2 ~]# curl 192.168.50.120:10080
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
...

查看同一台主机的负载均衡分配情况

修改默认web主页

# master1上的1号机
[root@vm1 ~]# docker exec -it nginx-cluster.1.6i1ncpnncxzxmsckwyahj9f7l bash
root@3ddd0e479de6:/# echo '#1 in master 1' > /usr/share/nginx/html/index.html

# master2上的2,3号
[root@vm2 ~]# docker exec -it nginx-cluster.2.gp7szi6348r0gfakr6v1i42ga bash
root@0d6709372322:/# echo '#2 in master 2' > /usr/share/nginx/html/index.html
root@0d6709372322:/#

[root@vm2 ~]# docker exec -it nginx-cluster.3.yofvioldzci3k4geve7lykyrs bash
root@6b1e246bdc34:/#  echo '#3 in master 2' > /usr/share/nginx/html/index.html

访问测试，访问#2的ip（轮询）

[root@vm2 ~]# curl 192.168.50.120:10080
#3 in master 2
[root@vm2 ~]# curl 192.168.50.120:10080
#1 in master 1
[root@vm2 ~]# curl 192.168.50.120:10080
#2 in master 2
[root@vm2 ~]# curl 192.168.50.120:10080
#3 in master 2

访问测试，访问#1的ip（轮询）

[root@vm2 ~]# curl 192.168.50.100:10080
#2 in master 2
[root@vm2 ~]# curl 192.168.50.100:10080
#1 in master 1
[root@vm2 ~]# curl 192.168.50.100:10080
#3 in master 2
[root@vm2 ~]# curl 192.168.50.100:10080
#2 in master 2

验证HA

关闭某个节点，看看容器会不会自动转移到其他可用节点

# 关闭master2之前

[root@vm2 ~]# docker ps
CONTAINER ID   IMAGE          COMMAND                  CREATED          STATUS          PORTS     NAMES
6b1e246bdc34   nginx:latest   "/docker-entrypoint.…"   18 minutes ago   Up 18 minutes   80/tcp    nginx-cluster.3.yofvioldzci3k4geve7lykyrs
0d6709372322   nginx:latest   "/docker-entrypoint.…"   18 minutes ago   Up 18 minutes   80/tcp    nginx-cluster.2.gp7szi6348r0gfakr6v1i42ga
[root@vm2 ~]#

# 关闭dockerd（模拟服务器宕机）

[root@vm2 ~]# systemctl stop docker
Warning: Stopping docker.service, but it can still be activated by:
  docker.socket

[root@vm2 ~]# systemctl status docker
● docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)

关闭#2号后，无法查看节点情况，此时处于尝试唤醒#2机dockerd服务的状态

[root@vm1 ~]# docker node ls
Error response from daemon: rpc error: code = DeadlineExceeded desc = context deadline exceeded

过一会儿，docker被唤醒

[root@vm2 ~]# systemctl status docker
● docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
   Active: active (running) since Sun 2022-01-23 13:22:38 JST; 28s ago

[root@vm1 ~]# docker node ls
ID                            HOSTNAME   STATUS    AVAILABILITY   MANAGER STATUS   ENGINE VERSION
kdcrkd6sqteevq9jgy70fd0h0 *   vm1        Ready     Active         Leader           20.10.12
4hh92oj2meotbi0etnje15bzq     vm2        Ready     Active         Reachable        20.10.12

关机看看

[root@vm2 ~]# shutdown -h now

网络完全不可通，#2状态为unreachable

[root@vm1 ~]# docker node ls
ID                            HOSTNAME   STATUS    AVAILABILITY   MANAGER STATUS   ENGINE VERSION
kdcrkd6sqteevq9jgy70fd0h0 *   vm1        Ready     Active         Leader           20.10.12
4hh92oj2meotbi0etnje15bzq     vm2        Ready     Active         Unreachable      20.10.12

只有一个master的时候无法执行service命令？？

[root@vm1 ~]# docker service ls
Error response from daemon: rpc error: code = Unknown desc = The swarm does not have a leader. It's possible that too few managers are online. Make sure more than half of the managers are online.

[root@vm1 ~]# docker node ls
Error response from daemon: rpc error: code = Unknown desc = The swarm does not have a leader. It's possible that too few managers are online. Make sure more than half of the managers are online.

下方的3台追加后【验证HA（3台变2台）】，都跑到#1上了

[root@vm1 ~]# docker ps
CONTAINER ID   IMAGE          COMMAND                  CREATED          STATUS          PORTS     NAMES
acc40b31df3f   nginx:latest   "/docker-entrypoint.…"   2 minutes ago    Up 2 minutes    80/tcp    nginx-cluster.3.ei48wkjvtmn53mfsjthlb52ef
d4635d8f2322   nginx:latest   "/docker-entrypoint.…"   2 minutes ago    Up 2 minutes    80/tcp    nginx-cluster.2.yyc2fmh73p23adbu44auuzf7r
3ddd0e479de6   nginx:latest   "/docker-entrypoint.…"   31 minutes ago   Up 31 minutes   80/tcp    nginx-cluster.1.6i1ncpnncxzxmsckwyahj9f7l

[root@vm1 ~]# docker node ls
ID                            HOSTNAME   STATUS    AVAILABILITY   MANAGER STATUS   ENGINE VERSION
kdcrkd6sqteevq9jgy70fd0h0 *   vm1        Ready     Active         Leader           20.10.12
4hh92oj2meotbi0etnje15bzq     vm2        Ready     Active         Reachable        20.10.12
lp4i21pj0sij9yz81f7u8dzy7     vm3        Ready     Active                          20.10.12

验证HA（3台变2台）

正常集群
[root@vm1 ~]# ip -br a | grep enp0s8 | awk '{print $3}'
192.168.50.100/24
CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES
[root@vm2 ~]# ip -br a | grep enp0s8 | awk '{print $3}'
192.168.50.120/24
[root@vm3 ~]# ip -br a | grep enp0s8 | awk '{print $3}'
192.168.50.130/24

[root@vm1 ~]# docker node ls
ID                            HOSTNAME   STATUS    AVAILABILITY   MANAGER STATUS   ENGINE VERSION
kdcrkd6sqteevq9jgy70fd0h0 *   vm1        Ready     Active         Leader           20.10.12
4hh92oj2meotbi0etnje15bzq     vm2        Ready     Active         Reachable        20.10.12
lp4i21pj0sij9yz81f7u8dzy7     vm3        Ready     Active                          20.10.12

创建一个服务（6台容器）

[root@vm1 ~]# docker service rm r4v6w094yxl3
r4v6w094yxl3

[root@vm1 ~]# docker service create --replicas 6 -p 10080:80 --network swarm-net --name nginx-cluster nginx                kzdm5zhgt1eo9goxy0rjwmklm
overall progress: 6 out of 6 tasks
1/6: running   [==================================================>]
2/6: running   [==================================================>]
3/6: running   [==================================================>]
4/6: running   [==================================================>]
5/6: running   [==================================================>]
6/6: running   [==================================================>]
verify: Service converged
[root@vm1 ~]#

各个主机上

[root@vm1 ~]# docker service ls
ID             NAME            MODE         REPLICAS   IMAGE          PORTS
kzdm5zhgt1eo   nginx-cluster   replicated   6/6        nginx:latest   *:10080->80/tcp

[root@vm3 ~]# docker service ls
Error response from daemon: This node is not a swarm manager. Worker nodes can't be used to view or modify cluster state. Please run this command on a manager node or promote the current node to a manager.


[root@vm1 ~]# docker ps
CONTAINER ID   IMAGE          COMMAND                  CREATED          STATUS          PORTS     NAMES
31177737f781   nginx:latest   "/docker-entrypoint.…"   28 seconds ago   Up 25 seconds   80/tcp    nginx-cluster.5.9a7wd7yqo4lweayw3352kssru
791b93b799d8   nginx:latest   "/docker-entrypoint.…"   28 seconds ago   Up 25 seconds   80/tcp    nginx-cluster.2.bcrt9chkfrmbjyy30n4g3il71

[root@vm2 ~]# docker ps
CONTAINER ID   IMAGE          COMMAND                  CREATED         STATUS         PORTS     NAMES
4a59afd4d2d2   nginx:latest   "/docker-entrypoint.…"   3 seconds ago   Up 2 seconds   80/tcp    nginx-cluster.1.c46oo5nzbchhbn6v07rft9d5b
bac746d67e4f   nginx:latest   "/docker-entrypoint.…"   4 seconds ago   Up 2 seconds   80/tcp    nginx-cluster.4.71wn1fz6yojbzunktws2qqslg


[root@vm3 ~]# docker ps
CONTAINER ID   IMAGE          COMMAND                  CREATED         STATUS         PORTS     NAMES
f0985bc21d07   nginx:latest   "/docker-entrypoint.…"   7 seconds ago   Up 5 seconds   80/tcp    nginx-cluster.6.vvykeb5g04gihc5jg4la26903
d14c20577a85   nginx:latest   "/docker-entrypoint.…"   7 seconds ago   Up 5 seconds   80/tcp    nginx-cluster.3.qwccv5u0jlwfp5txp5593d8cc
failover（worker）

假设#3宕机（worker）

[root@vm3 ~]# shutdown -h now

# 检查到主机down，可用依然为Active。。。

[root@vm1 ~]# docker node ls
ID                            HOSTNAME   STATUS    AVAILABILITY   MANAGER STATUS   ENGINE VERSION
kdcrkd6sqteevq9jgy70fd0h0 *   vm1        Ready     Active         Leader           20.10.12
4hh92oj2meotbi0etnje15bzq     vm2        Ready     Active         Reachable        20.10.12
lp4i21pj0sij9yz81f7u8dzy7     vm3        Down      Active                          20.10.12

# 服务器运行情况，加了2个容器顶替down掉了，共有8个容器

[root@vm1 ~]# docker service ls
ID             NAME            MODE         REPLICAS   IMAGE          PORTS
kzdm5zhgt1eo   nginx-cluster   replicated   8/6        nginx:latest   *:10080->80/tcp

# 平均分配到剩下的2台主机里

[root@vm1 ~]# docker ps
CONTAINER ID   IMAGE          COMMAND                  CREATED              STATUS              PORTS     NAMES
fce351b79e7a   nginx:latest   "/docker-entrypoint.…"   About a minute ago   Up About a minute   80/tcp    nginx-cluster.3.fr0a93dgk3bhiqv49q84ebo4o
31177737f781   nginx:latest   "/docker-entrypoint.…"   3 minutes ago        Up 3 minutes        80/tcp    nginx-cluster.5.9a7wd7yqo4lweayw3352kssru
791b93b799d8   nginx:latest   "/docker-entrypoint.…"   3 minutes ago        Up 3 minutes        80/tcp    nginx-cluster.2.bcrt9chkfrmbjyy30n4g3il71

[root@vm2 ~]# docker ps
CONTAINER ID   IMAGE          COMMAND                  CREATED              STATUS              PORTS     NAMES
3fee32911501   nginx:latest   "/docker-entrypoint.…"   About a minute ago   Up About a minute   80/tcp    nginx-cluster.6.p50b0kedcjmum7wrp6bprm6uf
4a59afd4d2d2   nginx:latest   "/docker-entrypoint.…"   3 minutes ago        Up 3 minutes        80/tcp    nginx-cluster.1.c46oo5nzbchhbn6v07rft9d5b
bac746d67e4f   nginx:latest   "/docker-entrypoint.…"   3 minutes ago        Up 3 minutes        80/tcp    nginx-cluster.4.71wn1fz6yojbzunktws2qqslg

假设#3修复后（worker）

# 运行中容器不会停止？3号机原来的容器没有设置自启动的话

[root@vm3 ~]# docker ps
CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES

# 启动后的#3的容器依然保留，但是在服务里的容器数由8变为6
[root@vm1 ~]# docker service ls
ID             NAME              MODE         REPLICAS   IMAGE          PORTS
kzdm5zhgt1eo   nginx-cluster     replicated   6/6        nginx:latest   *:10080->80/tcp

# 节点状态
[root@vm1 ~]# docker node ls
ID                            HOSTNAME   STATUS    AVAILABILITY   MANAGER STATUS   ENGINE VERSION
kdcrkd6sqteevq9jgy70fd0h0 *   vm1        Ready     Active         Leader           20.10.12
4hh92oj2meotbi0etnje15bzq     vm2        Ready     Active         Reachable        20.10.12
lp4i21pj0sij9yz81f7u8dzy7     vm3        Ready     Active                          20.10.12

# 此时新建服务的话，会优先分配到负载较低的#3机器（默认的负载时运行的容器数？）

[root@vm1 ~]# docker service create --replicas 2 -p 10081:80 --network swarm-net --name nginx-cluster-2 nginx              sfcq2vc5orxsgax5200mqtdbm
overall progress: 2 out of 2 tasks
1/2: running   [==================================================>]
2/2: running   [==================================================>]
verify: Service converged
[root@vm1 ~]#


[root@vm1 ~]# docker service ls
ID             NAME              MODE         REPLICAS   IMAGE          PORTS
kzdm5zhgt1eo   nginx-cluster     replicated   6/6        nginx:latest   *:10080->80/tcp
sfcq2vc5orxs   nginx-cluster-2   replicated   2/2        nginx:latest   *:10081->80/tcp

# #3只有一个容器，所以负载均衡的算法不是按数量的▲
[root@vm3 ~]# docker ps
CONTAINER ID   IMAGE          COMMAND                  CREATED              STATUS              PORTS     NAMES
e3465f370616   nginx:latest   "/docker-entrypoint.…"   About a minute ago   Up About a minute   80/tcp    nginx-cluster-2.1.twgr7jtplhr6c7i1cupymwf9k
删除某个容器
# 删除2号容器
[root@vm1 ~]# docker rm $(docker stop nginx-cluster-2.2.qs4tlxp1ilbtyd95xhkusjg48)
nginx-cluster-2.2.qs4tlxp1ilbtyd95xhkusjg48

# 在其他机器上自动新建
[root@vm2 ~]# docker ps
CONTAINER ID   IMAGE          COMMAND                  CREATED          STATUS          PORTS     NAMES
719e0941efa4   nginx:latest   "/docker-entrypoint.…"   20 seconds ago   Up 15 seconds   80/tcp    nginx-cluster-2.2.qc5tkdzdm0rcs0v57ue52n688

删除服务

服务没有停止的选项，也没有start。只能create和rm

[root@vm1 ~]# docker service --help
Usage:  docker service COMMAND
Manage services
Commands:
  create      Create a new service
  inspect     Display detailed information on one or more services
  logs        Fetch the logs of a service or task
  ls          List services
  ps          List the tasks of one or more services
  rm          Remove one or more services
  rollback    Revert changes to a service's configuration
  scale       Scale one or multiple replicated services
  update      Update a service

删除服务

[root@vm1 ~]# docker service rm nginx-cluster
nginx-cluster
[root@vm1 ~]# docker service ls
ID             NAME              MODE         REPLICAS   IMAGE          PORTS
sfcq2vc5orxs   nginx-cluster-2   replicated   2/2        nginx:latest   *:10081->80/tcp

# 通过服务创建的容器都被删除

[root@vm1 ~]# docker ps
CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES
[root@vm1 ~]# docker ps -a
CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES
[root@vm1 ~]#

[root@vm2 ~]# docker ps
CONTAINER ID   IMAGE          COMMAND                  CREATED         STATUS              PORTS     NAMES
719e0941efa4   nginx:latest   "/docker-entrypoint.…"   2 minutes ago   Up About a minute   80/tcp    nginx-cluster-2.2.qc5tkdzdm0rcs0v57ue52n688
[root@vm2 ~]# docker ps -a
CONTAINER ID   IMAGE          COMMAND                  CREATED         STATUS              PORTS     NAMES
719e0941efa4   nginx:latest   "/docker-entrypoint.…"   2 minutes ago   Up About a minute   80/tcp    nginx-cluster-2.2.qc5tkdzdm0rcs0v57ue52n688

手动停止容器

[root@vm2 ~]# docker ps
CONTAINER ID   IMAGE          COMMAND                  CREATED         STATUS         PORTS     NAMES
719e0941efa4   nginx:latest   "/docker-entrypoint.…"   4 minutes ago   Up 4 minutes   80/tcp    nginx-cluster-2.2.qc5tkdzdm0rcs0v57ue52n688

[root@vm2 ~]# docker stop nginx-cluster-2.2.qc5tkdzdm0rcs0v57ue52n688
nginx-cluster-2.2.qc5tkdzdm0rcs0v57ue52n688
[root@vm2 ~]# docker ps
CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES
[root@vm2 ~]#

# 几秒后，新的容器被创建

[root@vm2 ~]# docker ps
CONTAINER ID   IMAGE          COMMAND                  CREATED          STATUS          PORTS     NAMES
598c665b7a8e   nginx:latest   "/docker-entrypoint.…"   19 seconds ago   Up 13 seconds   80/tcp    nginx-cluster-2.2.qmgbury0aixey2sozive6377l

[root@vm2 ~]# docker ps -a
CONTAINER ID   IMAGE          COMMAND                  CREATED          STATUS                      PORTS     NAMES
598c665b7a8e   nginx:latest   "/docker-entrypoint.…"   24 seconds ago   Up 18 seconds               80/tcp    nginx-cluster-2.2.qmgbury0aixey2sozive6377l
719e0941efa4   nginx:latest   "/docker-entrypoint.…"   5 minutes ago    Exited (0) 24 seconds ago             nginx-cluster-2.2.qc5tkdzdm0rcs0v57ue52n688

[root@vm2 ~]# docker service ls
ID             NAME              MODE         REPLICAS   IMAGE          PORTS
sfcq2vc5orxs   nginx-cluster-2   replicated   2/2        nginx:latest   *:10081->80/tcp

如果再次把旧的容器启动的话

[root@vm2 ~]# docker start nginx-cluster-2.2.qc5tkdzdm0rcs0v57ue52n688
nginx-cluster-2.2.qc5tkdzdm0rcs0v57ue52n688
[root@vm2 ~]# docker ps
CONTAINER ID   IMAGE          COMMAND                  CREATED         STATUS         PORTS     NAMES
598c665b7a8e   nginx:latest   "/docker-entrypoint.…"   2 minutes ago   Up 2 minutes   80/tcp    nginx-cluster-2.2.qmgbury0aixey2sozive6377l
719e0941efa4   nginx:latest   "/docker-entrypoint.…"   7 minutes ago   Up 1 second    80/tcp    nginx-cluster-2.2.qc5tkdzdm0rcs0v57ue52n688

# 容器可以启动，但是集群已经将其抛弃

[root@vm2 ~]# docker service ls
ID             NAME              MODE         REPLICAS   IMAGE          PORTS
sfcq2vc5orxs   nginx-cluster-2   replicated   2/2        nginx:latest   *:10081->80/tcp

# 删除服务后，旧的容器一并删除

[root@vm2 ~]# docker service rm $(docker service ls -q)
sfcq2vc5orxs

[root@vm2 ~]# docker service ls
ID        NAME      MODE      REPLICAS   IMAGE     PORTS
[root@vm2 ~]# docker ps
CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES
[root@vm2 ~]# docker ps -a
CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES
[root@vm2 ~]#

其他

离开集群
[root@vm3 ~]# docker swarm leave
Error response from daemon: You are attempting to leave the swarm on a node that is participating as a manager. The only way to restore a swarm that has lost consensus is to reinitialize it with `--force-new-cluster`. Use `--force` to suppress this message.
[root@vm3 ~]# docker swarm leave --force

[root@vm3 ~]# docker node ls
Error response from daemon: This node is not a swarm manager. Use "docker swarm init" or "docker swarm join" to connect this node to swarm and try again.
删除集群

全部的节点都执行了leave命令后，集群就消失了

[root@vm1 ~]# docker swarm leave --force
Node left the swarm.

[root@vm1 ~]# docker node ls
Error response from daemon: This node is not a swarm manager. Use "docker swarm init" or "docker swarm join" to connect this node to swarm and try again.

QA

全部节点都设置为master？

只剩下一个节点（master或者worker）的时候，集群是不能管理的了？

具体容器在哪里跑只能上宿主机一台一台的docker ps查看？

docker service是保证服务时刻可用的，所有没有stop和start的选项，只有create和rm，通过docker stop和docker rm命令操作后，service会自动创建并启动新的容器（新的ID），运行中的容器消失，停止都被视为异常，都会新建容器来取代

代号223
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
docker swarm 搭建生产高可用的postgresql
lms99251的博客
10-29 1224
postgresql的数据量不大，单节点就能满足需求，但是单节点出现故障时，就会分悲催。故用docker swarm搭建一个高可用postgresql数据库，用两个主机节点来组，当一个节点故障自动迁移到另外一个节点，数据和配置文件都存放在glusterfs共享存储中。..................
docker 学习之-swarm集群搭建及测试
weixin_34233679的博客
03-29 413
swarm is a simple tool which controls a cluster of Docker hosts and exposes it as a single "virtual" host.就是一个docker集群管理工具。swarm的管理对象不是服务器层面而是集群层面的，指令只能是发送到集群，不能指定某个节点主机。 实验环境为3台虚拟机：安装系统为centos7 ；dock...
Docker swarm环境下部署JMETER集群-分布式压测
qq_39794423的博客
12-11 665
使用docker stack部署jmeter集群进行分布式压测
使用docker swarm创建集群并进行效果验证
greatfeather的专栏
02-27 3733
本文讲述了如何通过docker swarm来搭建容器集群，并进行了实际效果验证。
深入docker-swarm overlay网络模型
最新发布
weixin_42211693的博客
04-22 1090
overlay网络也被称为重叠网络或覆盖网络，是一种基于underlay网络之上的逻辑网络，既在物理网络的基础之上，通过节点间的单播隧道机制将主机两两相连形成的虚拟的，独立的网络。Docker swarm集群中的overlay网络主要是通过iptables，ipvs，vxlan等技术实现的，基于本身通信需求的网络模型。
Docker Swarm系列——4.Swarm服务检查
nloneday
11-19 2万+
文章目录1. 健康检查2. 创建服务 在这篇文章中，大家将会了解如何在服务中配置简单的命令进行容器定期自检，以表明当前容器是否处于健康状态。 1. 健康检查 通过前面几篇文章的理论和实践，大家都知道，Docker Swarm会自动判断服务中容器的健康状态，从而决定是否删除重建，以保证设定的副本数replicas。但它是怎么判断的呢？ 容器都有一个STATUS代表它的运行状态created, res...
docker swarm 集群搭建和试验
09-09
### Docker Swarm 集群搭建和试验 #### Docker Swarm 概述 Docker Swarm 是一个由 Docker 官方提供的用于创建 Docker 主机集群的工具。它具有多项关键特性，包括但不限于服务发现、负载均衡、任务分发与调度、服务...
详解Docker Swarm 在持续集成测试中的应用
09-30
本文主要介绍如何利用 Docker Swarm 集群功能和 Selenium Grid 脚本分发功能，来搭建一个可以动态扩容的 Selenium 自动化脚本执行环境，感兴趣的小伙伴们可以参考一下
Docker Swarm 在持续集成测试中的应用
12-29
主要介绍如何利用 Docker Swarm 集群功能和 Selenium Grid 脚本分发功能，来搭建一个可以动态扩容的 Selenium 自动化脚本执行环境。相比于用真实的机器作为 Selenium 自动化脚本执行环境，使用此套环境可以极大的...
Docker-Swarm部署与Ansible：将Docker Swarm部署在两节点或六节点的Raspberry Pi堆栈上，或部署在使用Vagrant的虚拟机上
02-06
尽管资源有限，但 Raspberry Pi 可以作为 Docker Swarm 集群的节点，尤其适合构建低成本的开发和测试环境。通过 Docker Swarm，可以在两个或六个 Raspberry Pi 上搭建集群，实现容器化应用的分布式部署。 **Ansible...
vagrant-boot2docker-swarm：多机Docker群Vagrant环境
02-06
9. **测试与调试**：学习如何在Vagrant环境中测试Docker Swarm集群的部署和服务，以及如何进行问题排查。 10. **持续集成/持续部署(CI/CD)**：探讨如何利用Vagrant和Docker Swarm实现应用的CI/CD流程，提高开发和...
Docker搭建Postgresql数据库
热门推荐
web
04-20 3万+
使用Docker搭建Postgresql数据库，及设置远程访问 一、拉取Postgresq镜像 docker pull postgres 二、构建镜像容器 docker run -it --name postgres --restart always -e POSTGRES_PASSWORD='abc123' -e ALLOW_IP_RANGE=0.0.0.0/0 -v /home/postgr...
Docker Swarm 编排及部署 PostGIS，并操作 GIS 数据
weixin_34128237的博客
05-27 117
本文还是继docker之后的一片更新，只是这次使用 Docker stack 进行容器部署及编排。部分图片来自 Docker 官网。 postgis 镜像的基础是 PostgreSql，所以我们部署了 postgis 镜像也就意味着有了 PostgreSql 数据库，在Docker Hub上已经有人为我们构建好了，我们拉取配置即可使用。 Swarm 是 ...
Error response from daemon: This node is not a swarm manager
撸起袖子加油干
05-03 9223
使用 overlay 网络，报错： docker network create -d overlay multihost Error response from daemon: This node is not a swarm manager. Use "docker swarm init" or "docker swarm join" to connect this node to swarm and try again. 解决方案： 执行：docker swarm init 找了...
docker操作异常集合
zsx18273117003的博客
08-13 653
1. 使用数据卷启动服务时出现异常 docker service create -d --replicas=4 --name devtest-service --mount sour ce=myvol2,target=/app nginx:latest 1.1 异常详情： Error response from daemon: This node is not a swarm manag...
docker swarm 网络设置
weixin_43931625的博客
08-22 2876
dockerswarm网络设置
docker swarm部署的docker服务无法访问外部的postgresql
johnhuster的专栏
01-06 1603
在使用portainer（docker swarm）方式部署thingsboard集群服务时发现tb-node节点无法访问外部的postgresql服务，通过docker logs containerId查看日志，找到了有效的日志：NO ROUTE TO HOST，通过docker exec -itcontainerId进入docker内部，执行ping postgresql服务Ip确实ping不通，但是却可以ping通其他ip。 也查了很多资料，很多说是postgresql配置问题，没有允许外部连接访.
Docker系列一：CentOS7安装Docker Swarm 集群及常用操作命令
u011745594的博客
10-31 9625
一、安装VMware 版本：VMware-workstation-full-12.0.0-2985596 二、安装CentOS 版本：CentOS-7-x86_64-Everything-1611 安装四个CentOS，1个manager结点，3个worker结点。 各个CentOS服务器信息如下： VMware安装CentOS服务器信息： manager     zy   192.
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值