Docker学习进阶(三) Docker网络

最新推荐文章于 2023-01-04 16:31:44 发布

一条没有梦想的闲鱼

最新推荐文章于 2023-01-04 16:31:44 发布

阅读量173

点赞数

分类专栏： docker 文章标签： docker

本文链接：https://blog.csdn.net/qq_41910252/article/details/116719965

版权

docker 专栏收录该内容

11 篇文章 0 订阅

订阅专栏

1.容器互联--link（不建议使用）

docker run -d -P --name tomcat02 --link tomcat01 tomcat

但是反过来tomcat01 去连 tomcat02 就ping不同了，他的实质就是在hosts文件配置了映射。

2.自定义网络

查看所有的docker网络

网络模式

bridge: 桥接模式这是docker自己本身的网络（默认）

none: 不配置网络

host: 主机模式和宿主机共享网络

测试

# 我们直接启动的命令，--net bridge ,而这个就是我们的docker0
docker run -d -P --name tomcat01 tomcat
docker run -d -P --name tomcat01 --net bridge tomcat

# docker0特点，默认，域名不允许访问，--link可以打通连接

我们可以自定义网络

docker network create --driver bridge --subnet 192.168.0.0/16  --gateway 192.168.0.1 mynet

然后我们查看自己创建的网络

docker network ls

查看网络信息

docker network inspect 网络名

然后我们把自己的容器放到自己创建的网络中

docker run -d -P --name tomcat-net-01 --net mynet tomcat

结论：我们自定义的网络docker都已经帮我们维护好了对应的关系。推荐我们平时使用自定义网络。

好处：不同的集群使用不同的网络，保证集群的安全和健康。

3.网络连通

docker network connect 网络 容器名

结论：假设要跨网络操作别人，就需要网络连通。

4. 实战：redis集群部署（分片+高可用+负载均衡）

1.创建自己redis网络

docker network create redis --subnet 172.38.0.0/16

2.查看是否创建成功

docker network ls

3. 查看网络信息

docker network inspect redis

4. 通过脚本创建6个redis配置

for port in $(seq 1 6); \
do \
mkdir -p /my/redis/node-${port}/conf
touch /my/redis/node-${port}/conf/redis.conf
cat << EOF >>/my/redis/node-${port}/conf/redis.conf
port 6379
bind 0.0.0.0
cluster-enabled yes
cluster-config-file nodes.conf
cluster-node-timeout 5000
cluster-announce-ip 172.38.0.1${port}
cluster-announce-port 6379
cluster-announce-bus-port 16379
appendonly yes
EOF
done

5.启动我们的redis容器

可以通过脚本来启动多个redis

docker run -p 637${port}:6379 -p 1637${port}:16379 --name redis-${prot} -v /my/redis/node-${port}/data:/data -v /my/redis/node-${port}/conf/redis.conf:/etc/redis/redis.conf -d --net redis --ip 172.38.0.1${port} redis:5.0.9-alpine3.11 redis-server /etc/redis/redis.conf

# 第一个节点
docker run -p 6371:6379 -p 16371:16379 --name redis-1 -v /my/redis/node-1/data:/data -v /my/redis/node-1/conf/redis.conf:/etc/redis/redis.conf -d --net redis --ip 172.38.0.11 redis:5.0.9-alpine3.11 redis-server /etc/redis/redis.conf

#第二个节点
docker run -p 6372:6379 -p 16372:16379 --name redis-2 -v /my/redis/node-2/data:/data -v /my/redis/node-2/conf/redis.conf:/etc/redis/redis.conf -d --net redis --ip 172.38.0.12 redis:5.0.9-alpine3.11 redis-server /etc/redis/redis.conf

。。。

6. 进入我们的容器来创建我们的集群

redis-cli --cluster create 172.38.0.11:6379 172.38.0.12:6379 172.38.0.13:6379 172.38.0.14:6379 172.38.0.15:6379 172.38.0.16:6379 --cluster-replicas 1

/data # redis-cli --cluster create 172.38.0.11:6379 172.38.0.12:6379 172.38.0.13:6379 172.38.0.14:6379 172.38.0.15:6379 172.38.0.16:6379 --cluster-replicas 1
>>> Performing hash slots allocation on 6 nodes...
Master[0] -> Slots 0 - 5460
Master[1] -> Slots 5461 - 10922
Master[2] -> Slots 10923 - 16383
Adding replica 172.38.0.15:6379 to 172.38.0.11:6379
Adding replica 172.38.0.16:6379 to 172.38.0.12:6379
Adding replica 172.38.0.14:6379 to 172.38.0.13:6379
M: dd6d664a1e57a358d4d560015b2a895a7375aebc 172.38.0.11:6379
   slots:[0-5460] (5461 slots) master
M: ca7123b12a8268dae62e3b287d4a42324ef1e422 172.38.0.12:6379
   slots:[5461-10922] (5462 slots) master
M: 9844750fc08788077da44b102d7d538887dfa970 172.38.0.13:6379
   slots:[10923-16383] (5461 slots) master
S: e53ff94625b1e9f53fa3638e10d16acf3a594c36 172.38.0.14:6379
   replicates 9844750fc08788077da44b102d7d538887dfa970
S: 18d047117d6e539496b2dedc99dcba25d750c795 172.38.0.15:6379
   replicates dd6d664a1e57a358d4d560015b2a895a7375aebc
S: db643e0cbc740814db6d1a810c771e604d5b31f6 172.38.0.16:6379
   replicates ca7123b12a8268dae62e3b287d4a42324ef1e422
Can I set the above configuration? (type 'yes' to accept): yes
>>> Nodes configuration updated
>>> Assign a different config epoch to each node
>>> Sending CLUSTER MEET messages to join the cluster
Waiting for the cluster to join
..
>>> Performing Cluster Check (using node 172.38.0.11:6379)
M: dd6d664a1e57a358d4d560015b2a895a7375aebc 172.38.0.11:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
S: 18d047117d6e539496b2dedc99dcba25d750c795 172.38.0.15:6379
   slots: (0 slots) slave
   replicates dd6d664a1e57a358d4d560015b2a895a7375aebc
M: 9844750fc08788077da44b102d7d538887dfa970 172.38.0.13:6379
   slots:[10923-16383] (5461 slots) master
   1 additional replica(s)
S: e53ff94625b1e9f53fa3638e10d16acf3a594c36 172.38.0.14:6379
   slots: (0 slots) slave
   replicates 9844750fc08788077da44b102d7d538887dfa970
S: db643e0cbc740814db6d1a810c771e604d5b31f6 172.38.0.16:6379
   slots: (0 slots) slave
   replicates ca7123b12a8268dae62e3b287d4a42324ef1e422
M: ca7123b12a8268dae62e3b287d4a42324ef1e422 172.38.0.12:6379
   slots:[5461-10922] (5462 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.

7. 测试

/data # redis-cli -c
127.0.0.1:6379> cluster info
cluster_state:ok
cluster_slots_assigned:16384
cluster_slots_ok:16384
cluster_slots_pfail:0
cluster_slots_fail:0
cluster_known_nodes:6
cluster_size:3
cluster_current_epoch:6
cluster_my_epoch:1
cluster_stats_messages_ping_sent:183
cluster_stats_messages_pong_sent:188
cluster_stats_messages_sent:371
cluster_stats_messages_ping_received:183
cluster_stats_messages_pong_received:183
cluster_stats_messages_meet_received:5
cluster_stats_messages_received:371
127.0.0.1:6379> cluster nodes
18d047117d6e539496b2dedc99dcba25d750c795 172.38.0.15:6379@16379 slave dd6d664a1e57a358d4d560015b2a895a7375aebc 0 1620987375000 5 connected
9844750fc08788077da44b102d7d538887dfa970 172.38.0.13:6379@16379 master - 0 1620987374654 3 connected 10923-16383
e53ff94625b1e9f53fa3638e10d16acf3a594c36 172.38.0.14:6379@16379 slave 9844750fc08788077da44b102d7d538887dfa970 0 1620987375656 4 connected
dd6d664a1e57a358d4d560015b2a895a7375aebc 172.38.0.11:6379@16379 myself,master - 0 1620987374000 1 connected 0-5460
db643e0cbc740814db6d1a810c771e604d5b31f6 172.38.0.16:6379@16379 slave ca7123b12a8268dae62e3b287d4a42324ef1e422 0 1620987375000 6 connected
ca7123b12a8268dae62e3b287d4a42324ef1e422 172.38.0.12:6379@16379 master - 0 1620987375000 2 connected 5461-10922
127.0.0.1:6379> set a b
-> Redirected to slot [15495] located at 172.38.0.13:6379
OK

#这时候我们看到这个值是存储在172.38.0.13(redis-3)这个节点上的，那这时候我们去把redis-3这个容器给停掉，看是否可以取到值
[root@iZuf6ecpsnuw5412vz7xhsZ /]# docker ps
CONTAINER ID        IMAGE                    COMMAND                  CREATED             STATUS              PORTS                                              NAMES
05e9a04d42ac        redis:5.0.9-alpine3.11   "docker-entrypoint..."   20 minutes ago      Up 20 minutes       0.0.0.0:6376->6379/tcp, 0.0.0.0:16376->16379/tcp   redis-6
c335eb6828c2        redis:5.0.9-alpine3.11   "docker-entrypoint..."   20 minutes ago      Up 20 minutes       0.0.0.0:6375->6379/tcp, 0.0.0.0:16375->16379/tcp   redis-5
961956ca6dcd        redis:5.0.9-alpine3.11   "docker-entrypoint..."   20 minutes ago      Up 20 minutes       0.0.0.0:6374->6379/tcp, 0.0.0.0:16374->16379/tcp   redis-4
2ffc7fe6a1e1        redis:5.0.9-alpine3.11   "docker-entrypoint..."   20 minutes ago      Up 20 minutes       0.0.0.0:6373->6379/tcp, 0.0.0.0:16373->16379/tcp   redis-3
33a36c407c8a        redis:5.0.9-alpine3.11   "docker-entrypoint..."   23 minutes ago      Up 23 minutes       0.0.0.0:6372->6379/tcp, 0.0.0.0:16372->16379/tcp   redis-2
9efd063f89ca        redis:5.0.9-alpine3.11   "docker-entrypoint..."   23 minutes ago      Up 23 minutes       0.0.0.0:6371->6379/tcp, 0.0.0.0:16371->16379/tcp   redis-1
[root@iZuf6ecpsnuw5412vz7xhsZ /]# docker stop redis-3
redis-3
[root@iZuf6ecpsnuw5412vz7xhsZ /]# docker ps
CONTAINER ID        IMAGE                    COMMAND                  CREATED             STATUS              PORTS                                              NAMES
05e9a04d42ac        redis:5.0.9-alpine3.11   "docker-entrypoint..."   20 minutes ago      Up 20 minutes       0.0.0.0:6376->6379/tcp, 0.0.0.0:16376->16379/tcp   redis-6
c335eb6828c2        redis:5.0.9-alpine3.11   "docker-entrypoint..."   20 minutes ago      Up 20 minutes       0.0.0.0:6375->6379/tcp, 0.0.0.0:16375->16379/tcp   redis-5
961956ca6dcd        redis:5.0.9-alpine3.11   "docker-entrypoint..."   21 minutes ago      Up 21 minutes       0.0.0.0:6374->6379/tcp, 0.0.0.0:16374->16379/tcp   redis-4
33a36c407c8a        redis:5.0.9-alpine3.11   "docker-entrypoint..."   24 minutes ago      Up 24 minutes       0.0.0.0:6372->6379/tcp, 0.0.0.0:16372->16379/tcp   redis-2
9efd063f89ca        redis:5.0.9-alpine3.11   "docker-entrypoint..."   24 minutes ago      Up 24 minutes       0.0.0.0:6371->6379/tcp, 0.0.0.0:16371->16379/tcp   redis-1
[root@iZuf6ecpsnuw5412vz7xhsZ /]# 

#我们已经把redis-3这个容器已经给停掉了。
127.0.0.1:6379> get a
-> Redirected to slot [15495] located at 172.38.0.14:6379
"b"
#这时候我们发现它是从172.38.0.14(redis-4)这个节点获取到的。在查看下nodes

172.38.0.14:6379> cluster nodes
ca7123b12a8268dae62e3b287d4a42324ef1e422 172.38.0.12:6379@16379 master - 0 1620988001570 2 connected 5461-10922
18d047117d6e539496b2dedc99dcba25d750c795 172.38.0.15:6379@16379 slave dd6d664a1e57a358d4d560015b2a895a7375aebc 0 1620988001269 1 connected
9844750fc08788077da44b102d7d538887dfa970 172.38.0.13:6379@16379 master,fail - 1620987719375 1620987717000 3 connected
e53ff94625b1e9f53fa3638e10d16acf3a594c36 172.38.0.14:6379@16379 myself,master - 0 1620988000000 7 connected 10923-16383
db643e0cbc740814db6d1a810c771e604d5b31f6 172.38.0.16:6379@16379 slave ca7123b12a8268dae62e3b287d4a42324ef1e422 0 1620988001000 6 connected
dd6d664a1e57a358d4d560015b2a895a7375aebc 172.38.0.11:6379@16379 master - 0 1620988001570 1 connected 0-5460

#发现172.38.0.13(redis-3)这个节点是已经挂掉了，172.38.0.14(redis-4)这个节点变成了主节点