发布时间：2025-12-09 19:19:43 浏览次数：4
Docker 是一个开源的应用容器引擎，让开发者可以打包他们的应用以及依赖包到一个可移植的镜像中，然后发布到任何流行的 Linux或Windows操作系统的机器上，也可以实现虚拟化。容器是完全使用沙箱机制，相互之间不会有任何接口。
基础名词：
镜像(image):
docker镜像就好比是一个模板，可以通过这个模板来创建容器服务，tomcat镜像 => run =>tomcat01容器（提供服务），通过这个镜像可以创建多个容器（最终服务运行或者项目运行就是在容器中的）。
容器(container):
Docker利用容器技术可以独立运行一个或者一组应用，通过镜像来创建的，启动，停止、删除、基本命令
目前就可以把这个容器理解为一个简易的linux系统
仓库(repository)
仓库就是存放镜像的地方！仓库分为公有和私有仓库！
Docker hub(默认是国外的) 阿里云…都有容器服务器（配置镜像加速！）
1、Docker有着比虚拟机更少的抽象层。
2、Docker利用的是虚拟主机的内核，vm需要是Guest OS。
所以说，新建的容器的时候，docker不需要虚拟机一样重新加载一个操作系统内核，避免引导。虚拟机是加载Guest OS，分钟级别，而docker是利用虚拟机主机的操作系统，忽略了这个复杂的过程，秒级别。
Docker 是一个Client-Server结构的系统，Docker的守护进程运行在主机上，通过Socket从客户端访问！
DockerServer接收到Docker-Client的指令，就会执行这个命令！
docker imgaes 查看所有镜像
[root@VM-4-8-centos ~]# docker imagesREPOSITORY TAG IMAGE ID CREATED SIZEhello-world latest feb5d9fea6a5 18 months ago 13.3kBcanal/canal-server v1.1.5 0c7f1d62a7d8 23 months ago 874MBmysql 5.7.25 98455b9624a9 4 years ago 372MB# 解释REPOSITORY 镜像的仓库源TAG 镜像的标签IMAGE ID 镜像的idCREATED 镜像的创建时间SIZE 镜像的大小# 可选项-a, --all# 列出所有镜像-f, --filter # 过滤-q, --quiet # 只显示镜像的iddocker pull 拉取镜像
# 指定版本拉取镜像 docker pull 镜像名[:tag] 不加标签，默认拉取最新版[root@VM-4-8-centos ~]# docker pull mysql:5.75.7: Pulling from library/mysql2ec521688c56: Pull complete f911f9b90db6: Pull complete 38eb4fe7ed26: Pull complete 01f772a6b25f: Pull complete 499456357ebf: Pull complete 274f3ad0dcec: Pull complete 3e6a5b12e1de: Pull complete de0c5c82dbbc: Pull complete c9bd281f4600: Pull complete 3289c4277a83: Pull complete 8b66f10a11fa: Pull complete Digest: sha256:1780318bdabc0edd36907bf91b47632eb912e8ea91258eca3590f8aca6f54836Status: Downloaded newer image for mysql:5.7docker.io/library/mysql:5.7docker rmi 删除镜像
# docker 执行删除镜像，根据id 或者名称docker rmi id# rmi删除不了正在使用的镜像，加-f强制删除docker rmi -f id# docker 执行批量删除镜像 通过递归方式进行删除docker rmi -f $(docker images -aq)先拉取一个镜像
docker pull centosdocker run [可选参数] image 新建容器并启动
docker run [可选参数] image# 参数说明--name="Name" 容器名称 tomcat01 tomcat02 ，用来区分容器-d 后端方式运行-it 使用交互方式运行，进入容器查看内容-小p 指定容器的端口 -p 8080:8080-p ip:主机端口:容器端口-p 主机端口:容器端口 (常用)-p 容器端口-大p 随机指定端口# 测试，启动并且进入容器[root@VM-4-8-centos ~]# docker run -p 9999 -it 5d0da3dc9764[root@4a098b3bac03 /]# lsbin dev etc home lib lib64 lost+found media mnt opt proc root run sbin srv sys tmp usr var# 使用exit退出容器命令[root@4a098b3bac03 /]# exitexitdocker ps 命令 列出所有容器
# 列出当前正在运行的容器docker ps 命令 -a# 列出当前正在运行的容器+带出历史运行过的容器-n=? # 显示最近创建的容器-q # 只显示容器的编号[root@VM-4-8-centos ~]# docker ps -aCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESacdfa099761b 5d0da3dc9764 "/bin/bash" 4 seconds ago Exited (0) 1 second ago thirsty_colden退出容器
exit # 直接容器停止并退出Ctrl + P + Q # 容器不停止退出删除容器
docker rm 容器id # 删除指定的容器，不能删除正在运行的容器，如果需要删除，则需要 rm -f 强制删除 docker rm -f $(docker ps -aq) # 删除所有的容器docker ps -a -q | xargs docker rm # 删除所有的容器启动和停止容器的操作
docker start 容器id # 启动容器docker restart 容器id # 重启容器docker stop 容器id # 停止容器docker kill 容器id # 强制杀死容器docker logs 容器id 查看日志的命令
docker logs 容器id#参数-f # 跟踪日志输出-n=? # 显示多少条日志，不写默认为all-t # 显示时间戳docker top 容器id 查看容器中进程信息
#docker top 容器id 是查看docker内部的信息[root@VM-4-8-centos ~]# docker top 52f808ba7f1aUID PID PPID C STIME TTY TIME CMDroot 22004 21983 0 10:39 pts/0 00:00:00 /bin/bashdocker inspect 容器id 镜像的元数据
# 命令 docker inspect 容器id# 测试[root@VM-4-8-centos ~]# docker inspect 52f808ba7f1a[{"Id": "52f808ba7f1a2419694fc0cd31d2fd8810a4456e5c8b0917096f5c80af164dff","Created": "2023-03-27T02:39:42.598864277Z","Path": "/bin/bash","Args": [],"State": {"Status": "running","Running": true,"Paused": false,"Restarting": false,"OOMKilled": false,"Dead": false,"Pid": 22004,"ExitCode": 0,"Error": "","StartedAt": "2023-03-27T02:39:42.943573356Z","FinishedAt": "0001-01-01T00:00:00Z"},"Image": "sha256:5d0da3dc976460b72c77d94c8a1ad043720b0416bfc16c52c45d4847e53fadb6","ResolvConfPath": "/var/lib/docker/containers/52f808ba7f1a2419694fc0cd31d2fd8810a4456e5c8b0917096f5c80af164dff/resolv.conf","HostnamePath": "/var/lib/docker/containers/52f808ba7f1a2419694fc0cd31d2fd8810a4456e5c8b0917096f5c80af164dff/hostname","HostsPath": "/var/lib/docker/containers/52f808ba7f1a2419694fc0cd31d2fd8810a4456e5c8b0917096f5c80af164dff/hosts","LogPath": "/var/lib/docker/containers/52f808ba7f1a2419694fc0cd31d2fd8810a4456e5c8b0917096f5c80af164dff/52f808ba7f1a2419694fc0cd31d2fd8810a4456e5c8b0917096f5c80af164dff-json.log","Name": "/suspicious_wright","RestartCount": 0,"Driver": "overlay2","Platform": "linux","MountLabel": "","ProcessLabel": "","AppArmorProfile": "","ExecIDs": null,"HostConfig": {"Binds": null,"ContainerIDFile": "","LogConfig": {"Type": "json-file","Config": {}},"NetworkMode": "default","PortBindings": {"9999/tcp": [{"HostIp": "","HostPort": ""}]},"RestartPolicy": {"Name": "no","MaximumRetryCount": 0},"AutoRemove": false,"VolumeDriver": "","VolumesFrom": null,"ConsoleSize": [25,188],"CapAdd": null,"CapDrop": null,"CgroupnsMode": "host","Dns": [],"DnsOptions": [],"DnsSearch": [],"ExtraHosts": null,"GroupAdd": null,"IpcMode": "private","Cgroup": "","Links": null,"OomScoreAdj": 0,"PidMode": "","Privileged": false,"PublishAllPorts": false,"ReadonlyRootfs": false,"SecurityOpt": null,"UTSMode": "","UsernsMode": "","ShmSize": 67108864,"Runtime": "runc","Isolation": "","CpuShares": 0,"Memory": 0,"NanoCpus": 0,"CgroupParent": "","BlkioWeight": 0,"BlkioWeightDevice": [],"BlkioDeviceReadBps": [],"BlkioDeviceWriteBps": [],"BlkioDeviceReadIOps": [],"BlkioDeviceWriteIOps": [],"CpuPeriod": 0,"CpuQuota": 0,"CpuRealtimePeriod": 0,"CpuRealtimeRuntime": 0,"CpusetCpus": "","CpusetMems": "","Devices": [],"DeviceCgroupRules": null,"DeviceRequests": null,"MemoryReservation": 0,"MemorySwap": 0,"MemorySwappiness": null,"OomKillDisable": false,"PidsLimit": null,"Ulimits": null,"CpuCount": 0,"CpuPercent": 0,"IOMaximumIOps": 0,"IOMaximumBandwidth": 0,"MaskedPaths": ["/proc/asound","/proc/acpi","/proc/kcore","/proc/keys","/proc/latency_stats","/proc/timer_list","/proc/timer_stats","/proc/sched_debug","/proc/scsi","/sys/firmware"],"ReadonlyPaths": ["/proc/bus","/proc/fs","/proc/irq","/proc/sys","/proc/sysrq-trigger"]},"GraphDriver": {"Data": {"LowerDir": "/var/lib/docker/overlay2/a8ec94947d108db6d6865b996ba0e1f9f29862e5a20741062d43e0f40bd33d92-init/diff:/var/lib/docker/overlay2/e20884d4e1b741ba886a96cdb9aacd515a0dc873e13e9ab457ba80dbeebe7ff6/diff","MergedDir": "/var/lib/docker/overlay2/a8ec94947d108db6d6865b996ba0e1f9f29862e5a20741062d43e0f40bd33d92/merged","UpperDir": "/var/lib/docker/overlay2/a8ec94947d108db6d6865b996ba0e1f9f29862e5a20741062d43e0f40bd33d92/diff","WorkDir": "/var/lib/docker/overlay2/a8ec94947d108db6d6865b996ba0e1f9f29862e5a20741062d43e0f40bd33d92/work"},"Name": "overlay2"},"Mounts": [],"Config": {"Hostname": "52f808ba7f1a","Domainname": "","User": "","AttachStdin": true,"AttachStdout": true,"AttachStderr": true,"ExposedPorts": {"9999/tcp": {}},"Tty": true,"OpenStdin": true,"StdinOnce": true,"Env": ["PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"],"Cmd": ["/bin/bash"],"Image": "5d0da3dc9764","Volumes": null,"WorkingDir": "","Entrypoint": null,"OnBuild": null,"Labels": {"org.label-schema.build-date": "20210915","org.label-schema.license": "GPLv2","org.label-schema.name": "CentOS Base Image","org.label-schema.schema-version": "1.0","org.label-schema.vendor": "CentOS"}},"NetworkSettings": {"Bridge": "","SandboxID": "47c564b6df75a68cbfbc3f707f4a86896008e565583fdf3a1b858ce4340431b0","HairpinMode": false,"LinkLocalIPv6Address": "","LinkLocalIPv6PrefixLen": 0,"Ports": {"9999/tcp": [{"HostIp": "0.0.0.0","HostPort": "32772"},{"HostIp": "::","HostPort": "32772"}]},"SandboxKey": "/var/run/docker/netns/47c564b6df75","SecondaryIPAddresses": null,"SecondaryIPv6Addresses": null,"EndpointID": "71b4819e81e4bf1d2475fee4fe982537dd6974f76f853deeafe704af0ceca649","Gateway": "172.17.0.1","GlobalIPv6Address": "","GlobalIPv6PrefixLen": 0,"IPAddress": "172.17.0.2","IPPrefixLen": 16,"IPv6Gateway": "","MacAddress": "02:42:ac:11:00:02","Networks": {"bridge": {"IPAMConfig": null,"Links": null,"Aliases": null,"NetworkID": "0a61313f17fe621a78c4756bb9b0461723747bd050c2ff8e2465736d17b103ce","EndpointID": "71b4819e81e4bf1d2475fee4fe982537dd6974f76f853deeafe704af0ceca649","Gateway": "172.17.0.1","IPAddress": "172.17.0.2","IPPrefixLen": 16,"IPv6Gateway": "","GlobalIPv6Address": "","GlobalIPv6PrefixLen": 0,"MacAddress": "02:42:ac:11:00:02","DriverOpts": null}}}}]进入当前正在运行的容器
# 我们通过从容器都是使用后台运行的，需要进入容器，修改一些配置# 方式一# docker exec -it 容器id bashShell[root@VM-4-8-centos ~]# docker exec -it 52f808ba7f1a /bin/bash[root@52f808ba7f1a /]# lsbin dev etc home lib lib64 lost+found media mnt opt proc root run sbin srv sys tmp usr var# 方式二docker attach 容器id# 测试[root@VM-4-8-centos ~]# docker attach 6cb0fea026f8 正在执行的代码.....# docker exec # 进入容器后开启一个新的终端，可以在里面操作（常用）# docker attach # 进入容器正在执行的终端，不会启动新的进程！从容器内拷贝文件到主机上
# docker cp 容器id:容器内路径 目的的主机路径[root@VM-4-8-centos ~]# docker psCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES52f808ba7f1a 5d0da3dc9764 "/bin/bash" 4 hours ago Up 4 hours 0.0.0.0:32772->9999/tcp, :::32772->9999/tcp suspicious_wright# 进入到容器内部[root@VM-4-8-centos ~]# docker attach 52f808ba7f1a[root@52f808ba7f1a /]# cd /home[root@52f808ba7f1a home]# ls# 在容器内部创建一个 test.java文件[root@52f808ba7f1a home]# touch test.java[root@52f808ba7f1a home]# lstest.java# 退出容器[root@52f808ba7f1a home]# exitexit[root@VM-4-8-centos ~]# cd /www[root@VM-4-8-centos www]# lsxxl-job# 将容器内部的文件进行拷贝到当前文件夹下面[root@VM-4-8-centos www]# docker cp 52f808ba7f1a:/home/test.java /wwwPreparing to copy...Successfully copied 1.536kB to /www[root@VM-4-8-centos www]# lstest.java xxl-job# 拷贝是一个手动过程，未来我们使用 -v 的技术，可以实现自动同步 /home /home端口暴露的原理
1、完成以后在浏览器输入: http://43.xxx.xxx.xxx:3344/ 进行访问
# 运行容器，需要做数据挂载！ # 安装启动mysql ， 需要配置密码的，这是需要注意的！# 官方测试： docker run --name some-mysql -e MYSQL_ROOT_PASSWORD=my-secret-pw -d mysql:tag# 启动mysql5.7-d 后台运行-p 端口映射-v 数据卷挂载-e 环境配置--name 容器名字[root@VM-4-8-centos test]# docker run -d -p 3306:3306 -v /www/mysql:/etc/mysql/conf.d -v /www/mysql:/var/lib/mysql -e MYSQL_ROOT_PASSWORD=456789 --name mysql01 mysql:5.7# 启动成功之后，查看linux发现文件已经关联上了# 使用Navicat连接到服务器3306 密码456789 --- 3306 和容器内部的 3306映射， 这个时候我们基于开源连接上了！# 在本地创建一个test数据库查看是否可以自动同步，看到本地已经出现test数据库的文件夹了，证明同步成功[root@VM-4-8-centos test]# cd /www/mysql/[root@VM-4-8-centos mysql]# lsauto.cnf ca.pem client-key.pem ibdata1 ib_logfile1 mysql performance_schema public_key.pem server-key.pem testca-key.pem client-cert.pem ib_buffer_pool ib_logfile0 ibtmp1 mysql.sock private_key.pem server-cert.pem sys结论： 我们发现，挂载到本地的数据卷一九没有丢失，这就实现了容器数据持久化！
所有的docker容器内的卷，没有指定目录的情况下都是在/var/lib/docker/volumes/_data
具名挂载
匿名挂载
拓展
dockerfile 就是用来构建docker镜像的构建文件！命令脚本！
通过这个脚本可以生成一个镜像，镜像是一层一层的，脚本一个个的命令组成，每个命令就是一层
注意：tag给镜像打标签的时候名字要严格按照官方文档给的写，否则报错denied: requested access to the resource is denied
# 登录阿里云镜像仓库[root@VM-4-8-centos ~]# docker login --username=filwaod1 registry.cn-hangzhou.aliyuncs.comPassword: WARNING! Your password will be stored unencrypted in /root/.docker/config.json.Configure a credential helper to remove this warning. Seehttps://docs.docker.com/engine/reference/commandline/login/#credentials-storeLogin Succeeded# 想拉取个nginx测试，报错，这里登录了阿里云，就是从阿里云的仓库拉取，但是阿里云的仓库没有这个镜像，所以报错# 解决方法，重新登录docker hub ，然后拉取nginx，再登录阿里云进行测试[root@VM-4-8-centos ~]# docker pull ngixnUsing default tag: latestError response from daemon: pull access denied for ngixn, repository does not exist or may require 'docker login': denied: requested access to the resource is denied# 登录docker hub 拉取nginx镜像[root@VM-4-8-centos ~]# docker login -u filwodPassword: WARNING! Your password will be stored unencrypted in /root/.docker/config.json.Configure a credential helper to remove this warning. Seehttps://docs.docker.com/engine/reference/commandline/login/#credentials-storeLogin Succeeded[root@VM-4-8-centos ~]# docker pull nginx[root@VM-4-8-centos ~]# docker imagesREPOSITORY TAG IMAGE ID CREATED SIZEnginx latest 080ed0ed8312 5 days ago 142MB# tag打标签[root@VM-4-8-centos ~]# docker tag 080ed0ed8312 registry.cn-hangzhou.aliyuncs.com/filwaod/test:1.0[root@VM-4-8-centos ~]# docker imagesREPOSITORY TAG IMAGE ID CREATED SIZEnginx latest 080ed0ed8312 5 days ago 142MBregistry.cn-hangzhou.aliyuncs.com/filwaod/test 1.0 080ed0ed8312 5 days ago 142MB# 推送阿里云[root@VM-4-8-centos ~]# docker push registry.cn-hangzhou.aliyuncs.com/filwaod/test:1.0其实xxxx.xxxx.xxxx.xxxx是一个十进制的数，我们就拿192.168.0.0/16来举例，192.168.0.0对应的二进制应该是11000000.10101000.00000000.00000000，那么后面的/16的意思就是前16位是不变的，只有后面16位是变动的，那么从11000000.10101000.00000000.00000000-11000000.10101000.11111111.11111111，对应的ip地址范围就是192.168.0.0-192.168.255.255，总共65534个可用ip（最后一位192.168.255.255为广播地址）。
如果是192.168.0.0/24，意思就是前24位是不变的，所对应的二进制的ip范围就是11000000.10101000.00000000.00000000-11000000.10101000.00000000.11111111,对应的ip地址就是192.168.0.0-192.168.0.0-192.168.0.255，共254个可用ip（最后一位192.168.0.255为广播地址）。
# 启动一个容器# 注意这里的tomcat镜像都是**版的镜像，# 执行docker exec -it tomcat01 ip addr会报错"OCI runtime exec failed: exec failed: unable to start container process: exe"docker run -d -P --name tomcat01 tomcat# 进入容器内部安装环境docker exec -it tomcat01 /bin/bash# apt 版本升级 root@e4487b29b91d:/usr/local/tomcat# apt update# 安装ip命令root@e4487b29b91d:/usr/local/tomcat# apt install -y iproute2# 安装ping命令root@e4487b29b91d:/usr/local/tomcat# apt-get install -y iputils-ping# 提交此镜像，后续启动都用这个镜像启动，就不用重新安装ip和ping命令了[root@VM-4-8-centos www]# docker ps -aCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESe4487b29b91d tomcat "catalina.sh run" 9 minutes ago Up 9 minutes 0.0.0.0:32770->8080/tcp, :::32770->8080/tcp tomcat01# 提交镜像[root@VM-4-8-centos www]# docker commit -a="cong" -m="test" e4487b29b91d mytomcatsha256:ea532f63ff6404af91f7791e090458dbab8cea2b923e5d68471031376c0399f9[root@VM-4-8-centos www]# docker imagesREPOSITORY TAG IMAGE ID CREATED SIZEmytomcat latest ea532f63ff64 7 seconds ago 524MBtomcat latest 608294908754 6 days ago 475MB# 查看容器内部的网络地址 ip addr[root@VM-4-8-centos www]# docker exec -it tomcat01 ip addr1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00inet 127.0.0.1/8 scope host lovalid_lft forever preferred_lft forever135: eth0@if136: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default link/ether 02:42:ac:11:00:02 brd ff:ff:ff:ff:ff:ff link-netnsid 0inet 172.17.0.2/16 brd 172.17.255.255 scope global eth0valid_lft forever preferred_lft forever# 思考： Linux能不能ping痛 容器内部 ? 是可以的原理
我们每启动一个docker容器， docker就会给docker容器分配一个ip， 我们只要安装了docker，就会有一个网卡 docker0桥接模式，使用的技术是veth-pair技术！
再启动一个容器测试， 发现又多了一对网卡，再次访问ip addr 命令
我们发现这个容器带来网卡，都是一对对的
veth-pair 就是一对的虚拟设备接口，他们都是成对出现的，一端连着协议，一端彼此相连
正因为有这个特性，veth-pair充当一个桥梁， 连接各种虚拟网络设备
OpenStac， Docker容器之间的链接，OVS的链接， 都是使用veth-pair技术
结论： 容器和容器之间是可以互相 ping 通的
绘制网络模型图
结论：tomcat01和tomcat02是共用的一个路由器，docker0
所有容器不指定网络的情况下，都是docker0路由的，doucker会给我们的容器分配一个默认的可用IP
Docker使用的是Linux的桥接，宿主机中是一个Docker容器的网桥docker0.
Docker中的所有的网络接口都是虚拟的，虚拟的转发效率高！（内网传递文件！）
只要容器删除，对应的网桥一对就没有了！
跟微服务注册中心一样，注册的是服务名，不管ip如何变化都能ping通
# 通过服务名ping[root@VM-4-8-centos ~]# docker exec -it tomcat02 ping tomcat01ping: tomcat01: Name or service not known# 如何可以解决呢？# 通过--link既可以解决网络连通问题[root@VM-4-8-centos ~]# docker run -d -P --name tomcat03 --link tomcat02 mytomcat3467d3c48f997062580ceef87c6a219315106c61cea903e94b4258d314e2ee66[root@VM-4-8-centos ~]# docker exec -it tomcat03 ping tomcat02PING tomcat02 (172.17.0.3) 56(84) bytes of data.64 bytes from tomcat02 (172.17.0.3): icmp_seq=1 ttl=64 time=0.085 ms64 bytes from tomcat02 (172.17.0.3): icmp_seq=2 ttl=64 time=0.048 ms64 bytes from tomcat02 (172.17.0.3): icmp_seq=3 ttl=64 time=0.046 ms^C--- tomcat02 ping statistics ---3 packets transmitted, 3 received, 0% packet loss, time 1999msrtt min/avg/max/mdev = 0.046/0.059/0.085/0.017 ms# 反向ping不通吗[root@VM-4-8-centos ~]# docker exec -it tomcat02 ping tomcat03ping: tomcat03: Name or service not known# 查看--link原理# hosts中增加了一个映射172.17.0.3 tomcat02 16dbd88c4c3e# 当ping tomcat02的时候，就会解析出ip为172.17.0.3，转而ping 172.17.0.3[root@VM-4-8-centos ~]# docker exec -it tomcat03 cat /etc/hosts127.0.0.1 localhost::1 localhost ip6-localhost ip6-loopbackfe00::0 ip6-localnetff00::0 ip6-mcastprefixff02::1 ip6-allnodesff02::2 ip6-allrouters172.17.0.3 tomcat02 16dbd88c4c3e172.17.0.4 3467d3c48f99网络模式
bridge： 桥接模式，桥接 docker 默认，自己创建的也是用brdge模式
none： 不配置网络
host： 和宿主机共享网络
container：容器网络连通！（用的少， 局限很大）
测试
# 我们直接启动的命令默认有一个 --net bridge，而这个就是我们的docker0docker run -d -P --name tomcat01 tomcatdocker run -d -P --name tomcat01 --net bridge tomcat# docker0特点，默认，容器名不能访问， --link可以打通连接！# 我们可以自定义一个网络！# --driver bridge# --subnet 192.168.0.0/16 可以支持255*255个网络 192.168.0.2 ~ 192.168.255.254# --gateway 192.168.0.1[root@VM-4-8-centos ~]# docker network create --driver bridge --subnet 192.168.0.0/16 --gateway 192.168.0.1 mynet8ad5de56f61189496ec5a13cca116254c08daf7b13d1b67bb1699ceb17fde821[root@VM-4-8-centos ~]# docker network lsNETWORK ID NAME DRIVER SCOPEca96fb03bd7e bridge bridge local9b8064b311dd host host local8ad5de56f611 mynet bridge localc41f634e7423 none null local[root@VM-4-8-centos ~]# docker network inspect mynet[{"Name": "mynet","Id": "8ad5de56f61189496ec5a13cca116254c08daf7b13d1b67bb1699ceb17fde821","Created": "2023-04-04T13:33:26.663075239+08:00","Scope": "local","Driver": "bridge","EnableIPv6": false,"IPAM": {"Driver": "default","Options": {},"Config": [{"Subnet": "192.168.0.0/16","Gateway": "192.168.0.1"}]},"Internal": false,"Attachable": false,"Ingress": false,"ConfigFrom": {"Network": ""},"ConfigOnly": false,"Containers": {},"Options": {},"Labels": {}}]# 在自己创建的网络中启动两个容器[root@VM-4-8-centos ~]# docker run -d -P --name tomcat-net-01 --net mynet mytomcat 587f553c019dd42fe763af7dd695882165542254c38f3268aff29de584a31c93[root@VM-4-8-centos ~]# docker run -d -P --name tomcat-net-02 --net mynet mytomcat 8da25fd4d62a6c218683ffae302fc241e3f900e7c4c10bf0e860b61eeefc1dfb[root@VM-4-8-centos ~]# docker network inspect mynet[{"Name": "mynet","Id": "8ad5de56f61189496ec5a13cca116254c08daf7b13d1b67bb1699ceb17fde821","Created": "2023-04-04T13:33:26.663075239+08:00","Scope": "local","Driver": "bridge","EnableIPv6": false,"IPAM": {"Driver": "default","Options": {},"Config": [{"Subnet": "192.168.0.0/16","Gateway": "192.168.0.1"}]},"Internal": false,"Attachable": false,"Ingress": false,"ConfigFrom": {"Network": ""},"ConfigOnly": false,"Containers": {"587f553c019dd42fe763af7dd695882165542254c38f3268aff29de584a31c93": {"Name": "tomcat-net-01","EndpointID": "450a64fea96fe830010ff9bcf63bbc7ec60201174bd4e75128b4733adafaeee6","MacAddress": "02:42:c0:a8:00:02","IPv4Address": "192.168.0.2/16","IPv6Address": ""},"8da25fd4d62a6c218683ffae302fc241e3f900e7c4c10bf0e860b61eeefc1dfb": {"Name": "tomcat-net-02","EndpointID": "de8c0dca95e17cd1b6419db00c08b38bf20dd8717d944e40c91543ccef302ca4","MacAddress": "02:42:c0:a8:00:03","IPv4Address": "192.168.0.3/16","IPv6Address": ""}},"Options": {},"Labels": {}}]# 现在ping名字可以ping通[root@VM-4-8-centos ~]# docker exec -it tomcat-net-01 ping tomcat-net-02PING tomcat-net-02 (192.168.0.3) 56(84) bytes of data.64 bytes from tomcat-net-02.mynet (192.168.0.3): icmp_seq=1 ttl=64 time=0.060 ms64 bytes from tomcat-net-02.mynet (192.168.0.3): icmp_seq=2 ttl=64 time=0.053 ms64 bytes from tomcat-net-02.mynet (192.168.0.3): icmp_seq=3 ttl=64 time=0.046 ms我们自定义的网络docker都已经帮我们维护好了对应的关系，推荐我们平时这样使用网络
好处：
redis - 不同的集群使用不同的网络，保证集群时安全和健康的
mysql - 不同的集群使用不同的网络，保证集群时安全和健康的
结论： 假设要跨网络操作别人，就需要使用 docker network connect 连通！
redis集群操作看我这篇文章：https://blog.csdn.net/qq_42665745/article/details/128844130
# 新建网络[root@VM-4-8-centos ~]# docker network create redis --subnet 172.38.0.0/16100cebc259381e6cd201a4ee523dbe908be83c6154327f95c2ec34a382bc2b93# 创建文件[root@VM-4-8-centos ~]# for port in $(seq 1 6); \> do \> mkdir -p /mydata/redis/node-${port}/conf> touch /mydata/redis/node-${port}/conf/redis.conf> cat << EOF >/mydata/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# 创建结点1docker run -p 6371:6379 -p 16371:16379 --name redis-1 \-v /mydata/redis/node-1/data:/data \-v /mydata/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#创建结点2docker run -p 6372:6379 -p 16372:16379 --name redis-2 \-v /mydata/redis/node-2/data:/data \-v /mydata/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#创建结点3docker run -p 6373:6379 -p 16373:16379 --name redis-3 \-v /mydata/redis/node-3/data:/data \-v /mydata/redis/node-3/conf/redis.conf:/etc/redis/redis.conf \-d --net redis --ip 172.38.0.13 redis:5.0.9-alpine3.11 redis-server /etc/redis/redis.conf#创建结点4docker run -p 6374:6379 -p 16374:16379 --name redis-4 \-v /mydata/redis/node-4/data:/data \-v /mydata/redis/node-4/conf/redis.conf:/etc/redis/redis.conf \-d --net redis --ip 172.38.0.14 redis:5.0.9-alpine3.11 redis-server /etc/redis/redis.conf#创建结点5docker run -p 6375:6379 -p 16375:16379 --name redis-5 \-v /mydata/redis/node-5/data:/data \-v /mydata/redis/node-5/conf/redis.conf:/etc/redis/redis.conf \-d --net redis --ip 172.38.0.15 redis:5.0.9-alpine3.11 redis-server /etc/redis/redis.conf#创建结点6docker run -p 6376:6379 -p 16376:16379 --name redis-6 \-v /mydata/redis/node-6/data:/data \-v /mydata/redis/node-6/conf/redis.conf:/etc/redis/redis.conf \-d --net redis --ip 172.38.0.16 redis:5.0.9-alpine3.11 redis-server /etc/redis/redis.conf# 进入redis-1内部[root@VM-4-8-centos ~]# docker exec -it redis-1 /bin/sh# 创建集群/data # /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# 查看集群配置/data # redis-cli cluster nodes8fd5ddc910e1dddd079d31e6993bd1eb9f555da4 172.38.0.13:6379@16379 master - 0 1680591047000 3 connected 10923-16383e977cd6987f9b45817c5926fd5c3a71635f5a0a0 172.38.0.12:6379@16379 master - 0 1680591048502 2 connected 5461-109222ffb5d03f17e30c825aca538ab2ee144c9223374 172.38.0.16:6379@16379 slave e977cd6987f9b45817c5926fd5c3a71635f5a0a0 0 1680591048501 6 connected5056347fe5605be313fe71861252a867e7880c16 172.38.0.15:6379@16379 slave 6df54e443a343bfa9a0339f10c10674b35bc418f 0 1680591048000 5 connectede323a154edaab137e51bc9ea6f428578534a9601 172.38.0.14:6379@16379 slave 8fd5ddc910e1dddd079d31e6993bd1eb9f555da4 0 1680591047000 4 connected6df54e443a343bfa9a0339f10c10674b35bc418f 172.38.0.11:6379@16379 myself,master - 0 1680591047000 1 connected 0-5460# 测试一下集群故障恢复# 连接redis-1 /data # redis-cli -c -p 6379# 设置值，值设置在了172.38.0.13这个容器上127.0.0.1:6379> set a 111-> Redirected to slot [15495] located at 172.38.0.13:6379OK# 新开一个窗口，停止172.38.0.13容器[root@VM-4-8-centos ~]# docker ps -aCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES488a48dc91fd redis:5.0.9-alpine3.11 "docker-entrypoint.s…" 35 minutes ago Up 35 minutes 0.0.0.0:6376->6379/tcp, :::6376->6379/tcp, 0.0.0.0:16376->16379/tcp, :::16376->16379/tcp redis-66b0916ec55cf redis:5.0.9-alpine3.11 "docker-entrypoint.s…" 35 minutes ago Up 35 minutes 0.0.0.0:6375->6379/tcp, :::6375->6379/tcp, 0.0.0.0:16375->16379/tcp, :::16375->16379/tcp redis-5f9db236a6dba redis:5.0.9-alpine3.11 "docker-entrypoint.s…" 35 minutes ago Up 35 minutes 0.0.0.0:6374->6379/tcp, :::6374->6379/tcp, 0.0.0.0:16374->16379/tcp, :::16374->16379/tcp redis-4bd47655a3409 redis:5.0.9-alpine3.11 "docker-entrypoint.s…" 35 minutes ago Up 35 minutes 0.0.0.0:6373->6379/tcp, :::6373->6379/tcp, 0.0.0.0:16373->16379/tcp, :::16373->16379/tcp redis-35ce5de87486c redis:5.0.9-alpine3.11 "docker-entrypoint.s…" 36 minutes ago Up 36 minutes 0.0.0.0:6372->6379/tcp, :::6372->6379/tcp, 0.0.0.0:16372->16379/tcp, :::16372->16379/tcp redis-2c6f20dcbd108 redis:5.0.9-alpine3.11 "docker-entrypoint.s…" 36 minutes ago Up 36 minutes 0.0.0.0:6371->6379/tcp, :::6371->6379/tcp, 0.0.0.0:16371->16379/tcp, :::16371->16379/tcp redis-1[root@VM-4-8-centos ~]# docker stop bd47655a3409bd47655a3409# 再查看集群配置/data # redis-cli cluster nodes8fd5ddc910e1dddd079d31e6993bd1eb9f555da4 172.38.0.13:6379@16379 master,fail - 1680591459812 1680591458000 3 connectede977cd6987f9b45817c5926fd5c3a71635f5a0a0 172.38.0.12:6379@16379 master - 0 1680591488000 2 connected 5461-109222ffb5d03f17e30c825aca538ab2ee144c9223374 172.38.0.16:6379@16379 slave e977cd6987f9b45817c5926fd5c3a71635f5a0a0 0 1680591487575 6 connected5056347fe5605be313fe71861252a867e7880c16 172.38.0.15:6379@16379 slave 6df54e443a343bfa9a0339f10c10674b35bc418f 0 1680591488979 5 connectede323a154edaab137e51bc9ea6f428578534a9601 172.38.0.14:6379@16379 master - 0 1680591489480 8 connected 10923-163836df54e443a343bfa9a0339f10c10674b35bc418f 172.38.0.11:6379@16379 myself,master - 0 1680591488000 1 connected 0-5460/data # redis-cli -c -p 6379127.0.0.1:6379> get a-> Redirected to slot [15495] located at 172.38.0.14:6379"111"1.随便找个springboot项目
2.打包并编写Dockerfile
3.复制jar和Dockerfile到同一目录下
4.打包
5.启动
[root@VM-4-8-centos springboot]# docker run -d -p 8082:8080 springboot090845ed70e6f14bb12a4cd1e5db5e560e5e3ffd3c6adf8d52ced2d824ba1d806.访问
免责声明：本站内容（文字信息+图片素材）来源于互联网公开数据整理或转载，仅用于学习参考，如有侵权问题，请及时联系本站删除，我们将在5个工作日内处理。联系邮箱：303555158#qq.com（把#换成@）
微信便捷交流