《Docker》高级篇
一、DockerFile
1.概述
DockerFile是用來構(gòu)建Docker鏡像的文本文件,是由一條條構(gòu)建鏡像所需的指令和參數(shù)構(gòu)成的腳本
1)鏡像構(gòu)建三步驟
213
2)DockerFile基礎(chǔ)知識
3)DockerFile執(zhí)行大概流程
4)DockerFile、鏡像、容器三者關(guān)系
Dockerfile、Docker鏡像與Docker容器分別代表軟件的三個不同階段,
- Dockerfile是軟件的原材料
- Docker鏡像是軟件的交付品
- Docker容器則可以認(rèn)為是軟件鏡像的運(yùn)行態(tài),也即依照鏡像運(yùn)行的容器實例
Dockerfile面向開發(fā),Docker鏡像成為交付標(biāo)準(zhǔn),Docker容器則涉及部署與運(yùn)維,三者缺一不可,合力充當(dāng)Docker體系的基石。
1 Dockerfile,需要定義一個Dockerfile,Dockerfile定義了進(jìn)程需要的一切東西。Dockerfile涉及的內(nèi)容包括執(zhí)行代碼或者是文件、環(huán)境變量、依賴包、運(yùn)行時環(huán)境、動態(tài)鏈接庫、操作系統(tǒng)的發(fā)行版、服務(wù)進(jìn)程和內(nèi)核進(jìn)程(當(dāng)應(yīng)用進(jìn)程需要和系統(tǒng)服務(wù)和內(nèi)核進(jìn)程打交道,這時需要考慮如何設(shè)計namespace的權(quán)限控制)等等;
2 Docker鏡像,在用Dockerfile定義一個文件之后,docker build時會產(chǎn)生一個Docker鏡像,當(dāng)運(yùn)行 Docker鏡像時會真正開始提供服務(wù);
3 Docker容器,容器是直接提供服務(wù)的。
2.指令
| FROM | 基礎(chǔ)鏡像,當(dāng)前新鏡像是基于哪個鏡像的,第一條必須是FROM |
| MAINTAINER | 鏡像維護(hù)者的姓名和郵箱地址 |
| RUN | 容器構(gòu)建docker build時需要運(yùn)行的命令 |
| WORKDIR | 登陸進(jìn)容器后的工作目錄 |
| ENV | 構(gòu)建鏡像過程中設(shè)置環(huán)境變量 |
| ADD | 將文件和目錄拷貝進(jìn)容器,并且可將壓縮文件解壓 |
| COPY* | 將文件和目錄拷貝進(jìn)容器,不會解壓文件 |
| VOLUME | 容器數(shù)據(jù)卷,用于數(shù)據(jù)保存和持久化工作 |
| CMD* | 容器運(yùn)行docker run時,指定一個容器啟動要運(yùn)行的命令,Dockerfile 中可以有多個 CMD 指令,但只有最后一個生效,CMD 會被 docker run 之后的參數(shù)替換 |
| ENTRYPOINT* | 容器運(yùn)行docker run時,指定一個容器啟動時要運(yùn)行的命令,ENTRYPOINT 的目的和 CMD 一樣,都是在指定容器啟動程序及參數(shù) |
| EXPOSE | 當(dāng)前容器對外暴露出的端口 |
3.Docker構(gòu)建/運(yùn)行命令
| 構(gòu)建 | docker build -t 新鏡像名字:TAG . |
| 運(yùn)行 | docker run -it 新鏡像名字:TAG |
4.案例
目的:下載Centos系統(tǒng),默認(rèn)不攜帶ifconfig、vim等命令,創(chuàng)建新鏡像,安裝這些命令的同時,配置JDK8
1) 配置
[root@localhost /]# docker pull centos Using default tag: latest latest: Pulling from library/centos a1d0c7532777: Pull complete Digest: sha256:a27fd8080b517143cbbbab9dfb7c8571c40d67d534bbdee55bd6c473f432b177 Status: Downloaded newer image for centos:latest docker.io/library/centos:latest [root@localhost myfile]# pwd /usr/local/myfile [root@localhost myfile]# touch Dockerfile #文件名首字母D大寫 [root@localhost myfile]# 通過其它工具上傳JDK的壓縮包 [root@localhost myfile]# ll 總用量 177108 -rw-r--r--. 1 root root 738 4月 9 10:35 Dockerfile -rw-r--r--. 1 root root 181352138 4月 9 10:26 jdk-8u101-linux-x64.tar.gz [root@localhost myfile]# vi Dockerfile 編寫DockerFile文件2) Dockerfile
FROM centos # 作者 MAINTAINER wang xxxqq.comENV MYPATH /usr/local WORKDIR $MYPATH# 安裝vim編輯器 RUN yum -y install vim # 安裝ifconfig命令查看網(wǎng)絡(luò)IP RUN yum -y install net-tools # 安裝java8及l(fā)ib庫 RUN yum -y install glibc.i686 RUN mkdir /usr/local/java # ADD 是相對路徑j(luò)ar,把jdk-8u171-linux-x64.tar.gz添加到容器中,安裝包必須要和Dockerfile文件在同一位置 ADD jdk-8u101-linux-x64.tar.gz /usr/local/java/ # 配置java環(huán)境變量 ENV JAVA_HOME /usr/local/java/jdk1.8 ENV JRE_HOME $JAVA_HOME/jre ENV CLASSPATH $JAVA_HOME/lib/dt.jar:$JAVA_HOME/lib/tools.jar:$JRE_HOME/lib:$CLASSPATH ENV PATH $JAVA_HOME/bin:$PATHEXPOSE 80CMD echo $MYPATH CMD echo "success--------------ok" CMD /bin/bash3) 構(gòu)建
構(gòu)建命令:docker build -t 新鏡像名稱:Tag .
[root@localhost myfile]# docker build -t centosjava8:1.5 . Sending build context to Docker daemon 181.4MB Step 1/14 : FROM centos---> 5d0da3dc9764 Step 2/14 : MAINTAINER wang xxxqq.com---> Using cache---> 375e94f40f2a Step 3/14 : ENV MYPATH /usr/local---> Using cache---> 432de48e379c Step 4/14 : WORKDIR $MYPATH---> Using cache---> ac3dd4d6aae2 Step 5/14 : RUN mkdir /usr/local/java---> Running in 7c5b7fd76465 Removing intermediate container 7c5b7fd76465---> ebbf73d9288d Step 6/14 : ADD jdk-8u101-linux-x64.tar.gz /usr/local/java/---> d89cfc2c386c Step 7/14 : ENV JAVA_HOME /usr/local/java/jdk1.8---> Running in eb354c97b752 Removing intermediate container eb354c97b752---> 05041c1edfb2 Step 8/14 : ENV JRE_HOME $JAVA_HOME/jre---> Running in ea628258c72a Removing intermediate container ea628258c72a---> 66149fd1f3c8 Step 9/14 : ENV CLASSPATH $JAVA_HOME/lib/dt.jar:$JAVA_HOME/lib/tools.jar:$JRE_HOME/lib:$CLASSPATH---> Running in 1c0b502bba17 Removing intermediate container 1c0b502bba17---> 07ab45bb1898 Step 10/14 : ENV PATH $JAVA_HOME/bin:$PATH---> Running in d75fe028140f Removing intermediate container d75fe028140f---> 0ec1d821aff3 Step 11/14 : EXPOSE 80---> Running in a0b173667afa Removing intermediate container a0b173667afa---> 29f94732eef3 Step 12/14 : CMD echo $MYPATH---> Running in 2c205bd28f1d Removing intermediate container 2c205bd28f1d---> 35b32de0a9ff Step 13/14 : CMD echo "success--------------ok"---> Running in b7410e84a412 Removing intermediate container b7410e84a412---> abe2bec57d8d Step 14/14 : CMD /bin/bash---> Running in 14065fd0a2a8 Removing intermediate container 14065fd0a2a8---> a38ae32cd3f8 Successfully built a38ae32cd3f8 Successfully tagged centosjava8:1.54) 運(yùn)行
[root@localhost myfile]# docker run -it centosjava8:1.5 /bin/bash5.虛懸鏡像
倉庫名和標(biāo)簽都是的鏡像被稱為虛懸鏡像,一般就是一些有問題的鏡像,沒啥用,之前有的面試官問過,虛懸鏡像直接刪除即可
下面通過Dockerfile創(chuàng)建一個虛懸鏡像測試
[root@localhost myxx]# pwd /usr/local/myxx [root@localhost myxx]# touch Dockerfile [root@localhost myxx]# vi Dockerfile [root@localhost myxx]# cat Dockerfile from ubuntu CMD echo 'action is success' [root@localhost myxx]# docker build . Sending build context to Docker daemon 2.048kB Step 1/2 : from ubuntu---> ba6acccedd29 Step 2/2 : CMD echo 'action is success'---> Running in 240b7fcd62b2 Removing intermediate container 240b7fcd62b2---> 1b9536b6a2d2 Successfully built 1b9536b6a2d2 [root@localhost myxx]# docker images REPOSITORY TAG IMAGE ID CREATED SIZE <none> <none> 1b9536b6a2d2 5 seconds ago 72.8MB查看所有的虛懸鏡像
[root@localhost myxx]# docker image ls -f dangling=true REPOSITORY TAG IMAGE ID CREATED SIZE <none> <none> 1b9536b6a2d2 50 seconds ago 72.8MB虛懸鏡像刪除
[root@localhost myxx]# docker image prune WARNING! This will remove all dangling images. Are you sure you want to continue? [y/N] y Deleted Images: deleted: sha256:1b9536b6a2d26270b57c09e92aa5883e75e2bd9317d09e02c85d11efa1a7fe8cTotal reclaimed space: 0B [root@localhost myxx]# docker image ls -f dangling=true REPOSITORY TAG IMAGE ID CREATED SIZE二、Docker微服務(wù)實戰(zhàn)
1.創(chuàng)建微服務(wù)
簡單通過IDEA創(chuàng)建一個SpringBoot工程,端口號6001,然后寫幾個簡單的接口,打成jar包
@RestController public class TestController {@Value("${server.port}")private String port;@GetMapping(value = "/docker/index")public String m1() {return port + ":微服務(wù) " + UUID.randomUUID().toString();}@GetMapping(value = "/docker/order")public String m2() {return port + ":微服務(wù) " + UUID.randomUUID().toString();}}2.微服務(wù)Docker部署
[root@localhost mydocker]# 將之前打成jar包的微服務(wù)上傳 [root@localhost mydocker]# pwd /usr/local/mydocker [root@localhost mydocker]# touch Dockerfile [root@localhost mydocker]# ll 總用量 17128 -rw-r--r--. 1 root root 17538487 4月 9 11:27 docker-boot.jar -rw-r--r--. 1 root root 0 4月 9 11:28 Dockerfile [root@localhost mydocker]# vi DockerfileDockerfile
# 基礎(chǔ)鏡像使用java FROM java:8 # 作者 MAINTAINER wang # VOLUME 指定臨時文件目錄為/tmp,在主機(jī)/var/lib/docker目錄下創(chuàng)建了一個臨時文件并鏈接到容器的/tmp VOLUME /tmp # 將jar包添加到容器中并更名為docker_boot_6001.jar ADD docker_boot.jar docker_boot_6001.jar # 運(yùn)行jar包 RUN bash -c 'touch /docker_boot_6001.jar' ENTRYPOINT ["java","-jar","/docker_boot_6001.jar"] #暴露6001端口作為微服務(wù) EXPOSE 6001構(gòu)建/運(yùn)行
[root@localhost mydocker]# docker build -t wang-docker:1.6 . #注意:最后面有個點(diǎn) Sending build context to Docker daemon 17.54MB Step 1/7 : FROM java:8---> d23bdf5b1b1b Step 2/7 : MAINTAINER wang---> Using cache---> 2b008d4e648c Step 3/7 : VOLUME /tmp---> Using cache---> d4647e658bc9 Step 4/7 : ADD docker_boot.jar docker_boot_6001.jar---> c3bc2caad1a8 Step 5/7 : RUN bash -c 'touch /docker_boot_6001.jar'---> Running in 1cdbc5d41cdb Removing intermediate container 1cdbc5d41cdb---> bb3ac09a6537 Step 6/7 : ENTRYPOINT ["java","-jar","/docker_boot_6001.jar"]---> Running in 2de424071939 Removing intermediate container 2de424071939---> 465a4e256351 Step 7/7 : EXPOSE 6001---> Running in d2bf767190cc Removing intermediate container d2bf767190cc---> 715ec2c3a847 Successfully built 715ec2c3a847 Successfully tagged wang-docker:1.6 [root@localhost mydocker]# docker images REPOSITORY TAG IMAGE ID CREATED SIZE wang-docker 1.6 715ec2c3a847 57 seconds ago 678MB [root@localhost mydocker]# docker run -d -p 6001:6001 wang-docker:1.6 3358618df7d8909c5f72983a137e3cefc52cc83c22ba0da4f080c5c010dbc6aa docker: Error response from daemon: driver failed programming external connectivity on endpoint priceless_kare (0740a1c5dfacb03fee3e92ca0798a85e5ffe5f7245d344c6576113ebcf1496f8): (iptables failed: iptables --wait -t nat -A DOCKER -p tcp -d 0/0 --dport 6001 -j DNAT --to-destination 172.17.0.3:6001 ! -i docker0: iptables: No chain/target/match by that name.(exit status 1)). [root@localhost mydocker]# systemctl stop firewalld [root@localhost mydocker]# systemctl restart docker #上面運(yùn)行碰到報錯了,關(guān)閉防火墻,重啟一下 [root@localhost mydocker]# docker run -d -p 6001:6001 wang-docker:1.6 2a8188d0604bf54685566df3a863c32f5a4e4cbab70edff391e61a6576b15feb [root@localhost mydocker]# curl 127.0.0.1:6001/docker/order #可以通過命令/網(wǎng)頁測試接口 6001:微服務(wù) be2bb438-2082-4382-bb16-f5f84e57d2dc三、Docker網(wǎng)絡(luò)
1.基礎(chǔ)介紹
首先學(xué)習(xí)Docker網(wǎng)絡(luò)為了解決的問題:
1.容器之間互聯(lián)和通信以及端口映射。容器可能在多個服務(wù)器上
2.容器IP變動的時候,可以通過服務(wù)名直接網(wǎng)絡(luò)通信而不受到影響
2.Docker network 命令
[root@localhost mydocker]# docker networkUsage: docker network COMMANDManage networksCommands:connect Connect a container to a network #連接網(wǎng)絡(luò)create Create a network #創(chuàng)建disconnect Disconnect a container from a network #斷開網(wǎng)絡(luò)inspect Display detailed information on one or more networks #查看網(wǎng)絡(luò)詳情ls List networks #查看網(wǎng)絡(luò)prune Remove all unused networks #刪除所有未使用的網(wǎng)絡(luò)rm Remove one or more networks #刪除網(wǎng)絡(luò)Run 'docker network COMMAND --help' for more information on a command.3.Docker network網(wǎng)絡(luò)模式
| bridge | 常用 | 為每一個容器分配、設(shè)置IP等,并將容器連接到一個docker 虛擬網(wǎng)橋,默認(rèn)為該模式 |
| host | 常用 | 容器將不會虛擬出自己的網(wǎng)卡,配置自己的IP等,而是使用宿主機(jī)的IP和端口 |
| none | 幾乎不用 | 容器有獨(dú)立的Network namespace,但并沒有對其進(jìn)行任何網(wǎng)絡(luò)設(shè)置,如分配veth pair和網(wǎng)絡(luò)連接,IP等 |
| container | 新創(chuàng)建的容器不會創(chuàng)建自己的網(wǎng)卡和配置自己的IP,而是和一個指定的容器共享IP、端口范圍等 |
1)bridge網(wǎng)絡(luò)模式
a)概念
1 Docker使用Linux橋接,在宿主機(jī)虛擬一個Docker容器網(wǎng)橋(docker0),Docker啟動一個容器時會根據(jù)Docker網(wǎng)橋的網(wǎng)段分配給容器一個IP地址,稱為Container-IP,同時Docker網(wǎng)橋是每個容器的默認(rèn)網(wǎng)關(guān)。因為在同一宿主機(jī)內(nèi)的容器都接入同一個網(wǎng)橋,這樣容器之間就能夠通過容器的Container-IP直接通信。
[root@localhost mydocker]# ifconfig #如果安裝了Docker,那么ifconfig會出現(xiàn)一個docker0網(wǎng)橋 docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255inet6 fe80::42:fff:fe7b:c329 prefixlen 64 scopeid 0x20<link>ether 02:42:0f:7b:c3:29 txqueuelen 0 (Ethernet)RX packets 165 bytes 11925 (11.6 KiB)RX errors 0 dropped 0 overruns 0 frame 0TX packets 118 bytes 9814 (9.5 KiB)TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 # 后面的省略了...2 docker run 的時候,沒有指定network的話默認(rèn)使用的網(wǎng)橋模式就是bridge,使用的就是docker0。在宿主機(jī)ifconfig,就可以看到docker0和自己create的network(后面講)eth0,eth1,eth2……代表網(wǎng)卡一,網(wǎng)卡二,網(wǎng)卡三……,lo代表127.0.0.1,即localhost,inet addr用來表示網(wǎng)卡的IP地址
3 網(wǎng)橋docker0創(chuàng)建一對對等虛擬設(shè)備接口一個叫veth,另一個叫eth0,成對匹配。
通過上述,將宿主機(jī)上的所有容器都連接到這個內(nèi)部網(wǎng)絡(luò)上,兩個容器在同一個網(wǎng)絡(luò)下,會從這個網(wǎng)關(guān)下各自拿到分配的ip,此時兩個容器的網(wǎng)絡(luò)是互通的。
b)案例
上面介紹docker0上面的veth0和容器內(nèi)部的eth0是兩兩配對的,那么驗證一下
[root@localhost mydocker]# docker run -d -p 8081:8080 --name tomcat81 billygoo/tomcat8-jdk8 01d73fb64a63f64a11a3db903e0c49bb377b90a8e190ed8364c34288a80b73d3 [root@localhost mydocker]# docker run -d -p 8082:8080 --name tomcat82 billygoo/tomcat8-jdk8 22229272719db15494e1a577e7bc0284e844875bd698e2d91ac86bfbb7de189b [root@localhost mydocker]# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 22229272719d billygoo/tomcat8-jdk8 "catalina.sh run" 2 minutes ago Up 2 minutes 0.0.0.0:8082->8080/tcp, :::8082->8080/tcp tomcat82 01d73fb64a63 billygoo/tomcat8-jdk8 "catalina.sh run" 3 minutes ago Up 2 minutes 0.0.0.0:8081->8080/tcp, :::8081->8080/tcp tomcat81在宿主機(jī)查看網(wǎng)絡(luò)
[root@localhost mydocker]# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1link/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 foreverinet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000link/ether 00:0c:29:d8:4d:70 brd ff:ff:ff:ff:ff:ffinet 192.168.146.144/24 brd 192.168.146.255 scope global dynamic ens33valid_lft 1171sec preferred_lft 1171secinet6 fe80::6fa4:e745:1e09:25bb/64 scope link valid_lft forever preferred_lft forever 3: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP link/ether 02:42:0f:7b:c3:29 brd ff:ff:ff:ff:ff:ffinet 172.17.0.1/16 brd 172.17.255.255 scope global docker0valid_lft forever preferred_lft foreverinet6 fe80::42:fff:fe7b:c329/64 scope link valid_lft forever preferred_lft forever 27: vethc7067a2@if26: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP link/ether 9a:f8:e8:6d:14:09 brd ff:ff:ff:ff:ff:ff link-netnsid 0inet6 fe80::98f8:e8ff:fe6d:1409/64 scope link valid_lft forever preferred_lft forever # 備注: 看到名稱29: veth4e385db@if28,代表宿主機(jī)的veth29對應(yīng)容器內(nèi)的eth0 28 29: veth4e385db@if28: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP link/ether 4e:45:d3:92:57:4f brd ff:ff:ff:ff:ff:ff link-netnsid 1inet6 fe80::4c45:d3ff:fe92:574f/64 scope link valid_lft forever preferred_lft forever # 備注: veth 31匹配eth0 30 31: veth5aa4302@if30: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP link/ether de:98:51:56:f7:73 brd ff:ff:ff:ff:ff:ff link-netnsid 2inet6 fe80::dc98:51ff:fe56:f773/64 scope link valid_lft forever preferred_lft forever [root@localhost mydocker]# docker inspect tomcat82 | tail -n 20"Networks": {"bridge": { #模式為bridge"IPAMConfig": null,"Links": null,"Aliases": null,"NetworkID": "d465af915f3662feb877915190ef94e4d11aee857ef342842d5c634f2ec07bd7","EndpointID": "f924ba305576beb8542a16c1cdb3377ba4bf8b9534e2b8da1de876d83e34379f","Gateway": "172.17.0.1","IPAddress": "172.17.0.4","IPPrefixLen": 16,"IPv6Gateway": "","GlobalIPv6Address": "","GlobalIPv6PrefixLen": 0,"MacAddress": "02:42:ac:11:00:04","DriverOpts": null}}}} ]tomcat81查看網(wǎng)絡(luò)
[root@localhost ~]# docker exec -it tomcat81 /bin/bash root@01d73fb64a63:/usr/local/tomcat# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1link/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 forever # 備注: 看到名稱,代表eth0 28對應(yīng)veth 29,和上面兩兩配對 28: eth0@if29: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default link/ether 02:42:ac:11:00:03 brd ff:ff:ff:ff:ff:ff link-netnsid 0inet 172.17.0.3/16 brd 172.17.255.255 scope global eth0valid_lft forever preferred_lft forever root@01d73fb64a63:/usr/local/tomcat#tomcat82查看網(wǎng)絡(luò)
[root@localhost ~]# docker exec -it tomcat82 /bin/bash root@22229272719d:/usr/local/tomcat# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1link/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 forever # 備注: eth0 30匹配veth 31 30: eth0@if31: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default link/ether 02:42:ac:11:00:04 brd ff:ff:ff:ff:ff:ff link-netnsid 0inet 172.17.0.4/16 brd 172.17.255.255 scope global eth0valid_lft forever preferred_lft forever2)host網(wǎng)絡(luò)模式
a)概念
容器將不會獲得一個獨(dú)立的Network Namespace, 而是和宿主機(jī)共用一個Network Namespace。容器將不會虛擬出自己的網(wǎng)卡而是使用宿主機(jī)的IP和端口。
b)案例
[root@localhost mydocker]# docker run -d -p 8083:8080 --network host --name tomcat83 billygoo/tomcat8-jdk8 WARNING: Published ports are discarded when using host network mode #這里的警告是我們既然使用host模式,那么自定義的端口映射就無所謂了,建議刪除 937164c67b2ff4754b42d5f8e29d8e2edd0de7568c1329fd222084326e0da6a3 [root@localhost mydocker]# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 937164c67b2f billygoo/tomcat8-jdk8 "catalina.sh run" 10 seconds ago Up 10 seconds tomcat83 [root@localhost mydocker]# docker inspect tomcat83 | tail -n 20 #查看狀態(tài)"Networks": {"host": { #模式為host模式"IPAMConfig": null,"Links": null,"Aliases": null,"NetworkID": "8a75ca97127fefe8c42def9a3c850f796ad425748ec2e6a9770de8c5490d38c5","EndpointID": "47ba09d49e2a639eb04485fc618c3c32bfe74d8aed483a50651141d733f933d3","Gateway": "","IPAddress": "","IPPrefixLen": 0,"IPv6Gateway": "","GlobalIPv6Address": "","GlobalIPv6PrefixLen": 0,"MacAddress": "","DriverOpts": null}}}} ]3)none網(wǎng)絡(luò)模式
禁用網(wǎng)絡(luò)功能,只有l(wèi)o標(biāo)識,就是127.0.0.1本地回環(huán),只能自己訪問
[root@localhost mydocker]# docker run -d -p 8084:8080 --network none --name tomcat84 billygoo/tomcat8-jdk8 7924c129d0d7dd400152ccc1f3849e5b7679371170fa6d3a8040b8abc2a87d5c [root@localhost mydocker]# docker exec -it tomcat84 bash root@7924c129d0d7:/usr/local/tomcat# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1link/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 forever4)container網(wǎng)絡(luò)模式
a)概念
新建的容器和已經(jīng)存在的一個容器共享一個網(wǎng)絡(luò)ip配置而不是和宿主機(jī)共享。新創(chuàng)建的容器不會創(chuàng)建自己的網(wǎng)卡,配置自己的IP,而是和一個指定的容器共享IP、端口范圍等。同樣,兩個容器除了網(wǎng)絡(luò)方面,其他的如文件系統(tǒng)、進(jìn)程列表等還是隔離的。
b)案例
這里再次使用tomcat演示,會報錯,因為兩個共用同一個ip,會導(dǎo)致端口沖突,所以這里使用Alpine演示,Alpine操作系統(tǒng)是一個面向安全的輕型Linux發(fā)行版
啟動alpine1
[root@localhost mydocker]# docker run -it --name alpine1 alpine / # ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1link/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 forever 34: eth0@if35: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP link/ether 02:42:ac:11:00:05 brd ff:ff:ff:ff:ff:ffinet 172.17.0.5/16 brd 172.17.255.255 scope global eth0valid_lft forever preferred_lft forever / #啟動alpine2
可以看到兩個容器共用同一組eth和evth
[root@localhost ~]# docker run -it --network container:alpine1 --name alpine2 alpine /bin/sh / # ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1link/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 forever 34: eth0@if35: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP link/ether 02:42:ac:11:00:05 brd ff:ff:ff:ff:ff:ffinet 172.17.0.5/16 brd 172.17.255.255 scope global eth0valid_lft forever preferred_lft forever / #此時停掉alpine1
[root@localhost ~]# docker stop alpine1 alpine1查看alpine2
發(fā)現(xiàn)alpine2只有l(wèi)o了
/ # ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1link/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 forever / #4.自定義網(wǎng)絡(luò)
我們兩個容器實例,相互之間,可以根據(jù)ip來ping通,那么一旦容器的ip發(fā)生變化,那么我們的配置也要更改,那么就需要根據(jù)容器實例名稱來ping通,那么就需要借助自定義網(wǎng)絡(luò)來實現(xiàn)
before
啟動兩個容器實例
[root@localhost mydocker]# docker run -d -p 8091:8080 --name tomcat91 billygoo/tomcat8-jdk8 1f5f099f432de34032c89ef0124211238dc672c58567a1d5e94be85110618b72 [root@localhost mydocker]# docker run -d -p 8092:8080 --name tomcat92 billygoo/tomcat8-jdk8 c98db87419676303021443ae0fd84a9383678e9e3b4c5c00150ce68d82d1d8d6進(jìn)入到tomcat91,
進(jìn)入到tomcat92
自定義橋接網(wǎng)絡(luò)
自定義橋接網(wǎng)絡(luò),自定義網(wǎng)絡(luò)默認(rèn)使用的是橋接網(wǎng)絡(luò)bridge
[root@localhost ~]# docker network create wang_network dc3f93953365d7f0509fa1642ae0bed7286426a0068a0925bcceeb9e1d327c0a [root@localhost ~]# docker network ls NETWORK ID NAME DRIVER SCOPE d465af915f36 bridge bridge local 8a75ca97127f host host local e593b981f4cd none null local dc3f93953365 wang_network bridge localafter
創(chuàng)建容器實例,指定網(wǎng)絡(luò)模式為自定義的wang_network
[root@localhost mydocker]# docker run -d -p 8093:8080 --network wang_network --name tomcat93 billygoo/tomcat8-jdk8 a4daff881e51f9cf52f46a52b2e2757a63fc27f18d60b75e78367364196f84dd [root@localhost mydocker]# docker run -d -p 8094:8080 --network wang_network --name tomcat94 billygoo/tomcat8-jdk8 2594522015d3eb11ffe0abc0bf61fcd5bdbd4ad436f6458e7c144060402145e4進(jìn)入到tomcat93
進(jìn)入到tomcat94
四、Docker-compose容器編排
1.簡介
Docker-compose是Docker官方的開源項目,負(fù)責(zé)實現(xiàn)對Docker容器集群的快速編排,可以管理多個 Docker 容器組成一個應(yīng)用。你需要定義一個 YAML 格式的配置文件docker-compose.yml,寫好多個容器之間的調(diào)用關(guān)系。然后,只要一個命令,就能同時啟動/關(guān)閉這些容器
簡單點(diǎn)說:Dockerfile用于構(gòu)建單個鏡像,那么Compose用于多個鏡像一鍵部署
2.下載/安裝
https://docs.docker.com/compose/compose-file/compose-file-v3/
https://docs.docker.com/compose/install/
安裝步驟很簡單,按照官網(wǎng)的說明,兩三步就完事
[root@localhost mydocker]# curl -L "https://github.com/docker/compose/releases/download/1.29.2/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose% Total % Received % Xferd Average Speed Time Time Time CurrentDload Upload Total Spent Left Speed 100 664 100 664 0 0 983 0 --:--:-- --:--:-- --:--:-- 985 100 12.1M 100 12.1M 0 0 5129k 0 0:00:02 0:00:02 --:--:-- 7466k [root@localhost mydocker]# chmod +x /usr/local/bin/docker-compose [root@localhost mydocker]# docker-compose --version docker-compose version 1.29.2, build 5becea4c [root@localhost mydocker]#3.Compose使用三個步驟
4.Compose常用命令
docker-compose -h # 查看幫助docker-compose up # 啟動所有docker-compose服務(wù)docker-compose up -d # 啟動所有docker-compose服務(wù)并后臺運(yùn)行docker-compose down # 停止并刪除容器、網(wǎng)絡(luò)、卷、鏡像。docker-compose exec yml里面的服務(wù)id # 進(jìn)入容器實例內(nèi)部 docker-compose exec docker-compose.yml文件中寫的服務(wù)id /bin/bashdocker-compose ps # 展示當(dāng)前docker-compose編排過的運(yùn)行的所有容器docker-compose top # 展示當(dāng)前docker-compose編排過的容器進(jìn)程docker-compose logs yml里面的服務(wù)id # 查看容器輸出日志docker-compose config # 檢查配置docker-compose config -q # 檢查配置,有問題才有輸出docker-compose restart # 重啟服務(wù)docker-compose start # 啟動服務(wù)docker-compose stop # 停止服務(wù)5.Compose編排微服務(wù)測試
為了測試容器編排,那么肯定需要多個容器,這里使用 微服務(wù) + Mysql容器 + Redis容器
然后一個最常見的例子,通過接口查詢數(shù)據(jù),緩存存在則返回,否則去查詢數(shù)據(jù)庫
1)微服務(wù)調(diào)整
代碼很簡單,查詢Mysql或者Redis,主要調(diào)整一下配置
server.port=6001 # ========================alibaba.druid相關(guān)配置===================== spring.datasource.type=com.alibaba.druid.pool.DruidDataSource spring.datasource.driver-class-name=com.mysql.jdbc.Driver #spring.datasource.url=jdbc:mysql://192.168.146.144:3306/db01?useUnicode=true&characterEncoding=utf-8&useSSL=false spring.datasource.url=jdbc:mysql://mysql:3306/db01?useUnicode=true&characterEncoding=utf-8&useSSL=false spring.datasource.username=root spring.datasource.password=123456 spring.datasource.druid.test-while-idle=false # ========================redis相關(guān)配置===================== spring.redis.database=0 spring.redis.host=192.168.146.144 spring.redis.port=6379 spring.redis.password=123456 spring.redis.lettuce.pool.max-active=8 spring.redis.lettuce.pool.max-wait=-1ms spring.redis.lettuce.pool.max-idle=8 spring.redis.lettuce.pool.min-idle=0 # ========================mybatis相關(guān)配置=================== mybatis.mapper-locations=classpath:mapper/*.xml2)微服務(wù)代碼生成
創(chuàng)建微服務(wù)的鏡像
[root@localhost mydocker]# ll 總用量 37056 drwxr-xr-x. 2 root root 6 4月 10 16:25 data -rw-r--r--. 1 root root 37937917 4月 10 16:54 docker_boot.jar -rw-r--r--. 1 root root 454 4月 10 16:54 Dockerfile [root@localhost mydocker]# cat Dockerfile # 基礎(chǔ)鏡像使用java FROM java:8 # 作者 MAINTAINER wang # VOLUME 指定臨時文件目錄為/tmp,在主機(jī)/var/lib/docker目錄下創(chuàng)建了一個臨時文件并鏈接到容器的/tmp VOLUME /tmp # 將jar包添加到容器中并更名為docker_boot_6001.jar ADD docker_boot.jar docker_boot_6001.jar # 運(yùn)行jar包 RUN bash -c 'touch /docker_boot_6001.jar' ENTRYPOINT ["java","-jar","/docker_boot_6001.jar"] #暴露6001端口作為微服務(wù) EXPOSE 6001 [root@localhost mydocker]# docker build -t docker-boot:1.6 . Sending build context to Docker daemon 37.94MB Step 1/7 : FROM java:8---> d23bdf5b1b1b Step 2/7 : MAINTAINER wang---> Running in 9dc0bbc28c31 Removing intermediate container 9dc0bbc28c31---> 3fd2345a2b2b Step 3/7 : VOLUME /tmp---> Running in 37fd3a68f844 Removing intermediate container 37fd3a68f844---> a2a317bea03d Step 4/7 : ADD docker_boot.jar docker_boot_6001.jar---> 5a9b3a17f228 Step 5/7 : RUN bash -c 'touch /docker_boot_6001.jar'---> Running in 414c693f05d5 Removing intermediate container 414c693f05d5---> a4f9dae9f002 Step 6/7 : ENTRYPOINT ["java","-jar","/docker_boot_6001.jar"]---> Running in 5e4efb0b311b Removing intermediate container 5e4efb0b311b---> a1a744191f83 Step 7/7 : EXPOSE 6001---> Running in 5e3ca39a95eb Removing intermediate container 5e3ca39a95eb---> d37ba7b0e15d Successfully built d37ba7b0e15d Successfully tagged docker-boot:1.63)鏡像準(zhǔn)備
之前已經(jīng)創(chuàng)建了微服務(wù)的鏡像,接下來在拉取一下Mysql和Redis的鏡像
[root@localhost compose]# docker images REPOSITORY TAG IMAGE ID CREATED SIZE docker-boot 1.6 d37ba7b0e15d About a minut 719MB mysql 5.7 c20987f18b13 3 months ago 448MB redis 6.0.8 16ecd2772934 17 months ago 104MB4)docker-compose.yml
[root@localhost compose]# pwd /usr/local/compose [root@localhost compose]# ll 總用量 4 -rw-r--r--. 1 root root 980 4月 10 16:28 docker-compose.ymldocker-compose內(nèi)容
version: "3"services:dockerboot:image: docker-boot:1.6container_name: boot-composeports:- "6001:6001"volumes:- /usr/local/mydocker/data:/datanetworks: - wan_network depends_on: - redis- mysqlredis:image: redis:6.0.8container_name: redis-composeprivileged: trueports:- "6379:6379"volumes:- /usr/local/redis/redis.conf:/etc/redis/redis.conf- /usr/local/redis/data:/datanetworks: - wan_networkcommand: redis-server /etc/redis/redis.confmysql:image: mysql:5.7container_name: mysql-composeenvironment:MYSQL_ROOT_PASSWORD: '123456'MYSQL_ALLOW_EMPTY_PASSWORD: 'no'MYSQL_DATABASE: 'db01'ports:- "3306:3306"volumes:- /usr/local/mysql/data:/var/lib/mysql- /usr/local/mysql/conf:/etc/mysql/conf.d- /usr/local/mysql/my.cnf:/etc/mysql/my.cnfnetworks:- wan_networkcommand: --default-authentication-plugin=mysql_native_password networks: wan_network:5)compose啟動
[root@localhost compose]# pwd /usr/local/compose [root@localhost compose]# ll 總用量 4 -rw-r--r--. 1 root root 980 4月 10 17:24 docker-compose.yml [root@localhost compose]# docker-compose up -d Creating network "compose_wan_network" with the default driver Creating mysql-compose ... done Creating redis-compose ... done Creating boot-compose ... done [root@localhost compose]# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 559738e75210 docker-boot:1.6 "java -jar /docker_b…" 5 seconds ago Up 3 seconds 0.0.0.0:6001->6001/tcp, :::6001->6001/tcp boot-compose bd0b15d9cf22 mysql:5.7 "docker-entrypoint.s…" 6 seconds ago Up 5 seconds 0.0.0.0:3306->3306/tcp, :::3306->3306/tcp, 33060/tcp mysql-compose五、Docker輕量級可視化工具Portainer
Portainer 是一款輕量級的應(yīng)用,它提供了圖形化界面,用于方便地管理Docker環(huán)境,包括單機(jī)環(huán)境和集群環(huán)境。
1.安裝
https://www.portainer.io/
[root@localhost mydocker]# docker pull portainer/portainer Using default tag: latest latest: Pulling from portainer/portainer 94cfa856b2b1: Pull complete 49d59ee0881a: Pull complete a2300fd28637: Pull complete Digest: sha256:fb45b43738646048a0a0cc74fcee2865b69efde857e710126084ee5de9be0f3f Status: Downloaded newer image for portainer/portainer:latest docker.io/portainer/portainer:latest [root@localhost mydocker]# docker run -d -p 8000:8000 -p 9000:9000 \--name portainer --restart=always \-v /var/run/docker.sock:/var/run/docker.sock \-v portainer_data:/data \portainer/portainer b4593ae49a4be51a82035955989fa73cd9f75715964465f299ce1a1b2780bdbb [root@localhost mydocker]# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES b4593ae49a4b portainer/portainer "/portainer" 39 seconds ago Up 37 seconds 0.0.0.0:8000->8000/tcp, :::8000->8000/tcp, 0.0.0.0:9000->9000/tcp, :::9000->9000/tcp portainer2.訪問
創(chuàng)建成功以后,訪問地址: http://192.168.146.144:9000,第一次登陸需要創(chuàng)建用戶,輸入自己的密碼即可,然后登陸訪問
3.使用
功能非常強(qiáng)大,可以在界面拉取鏡像,創(chuàng)建容器實例,之前都是通過命令來操作,現(xiàn)在界面輸入即可
六、Docker重量級容器監(jiān)控之
CAdvisor監(jiān)控收集 + Influx存儲數(shù)據(jù) + Granfana展示圖表
小公司無所謂了
使用的時候再去看視頻了
總結(jié)
以上是生活随笔為你收集整理的《Docker》高级篇的全部內(nèi)容,希望文章能夠幫你解決所遇到的問題。
- 上一篇: Katana概述
- 下一篇: win7旗舰版 OEM KEY