Docker 深入浅出系列 | Image 实战演练（docker image inspect）

25-03-10 13

在本文中，我们将给您介绍关于Docker深入浅出系列|Image实战演练的详细内容，并且为您解答dockerimageinspect的相关问题，此外，我们还将为您提供关于#Docker#深入浅出、(奇

在本文中，我们将给您介绍关于Docker 深入浅出系列 | Image 实战演练的详细内容，并且为您解答docker image inspect的相关问题，此外，我们还将为您提供关于#Docker# 深入浅出、(奇淫技巧)Docker的深入浅出、25.week4 docker build 也就是创建自己的image 上传image到dockerhub 从dockerhub下载images、ASP.NET Core使用Docker-Swarm集群部署实现负载均衡实战演练的知识。

本文目录一览：

Docker 深入浅出系列 | Image 实战演练（docker image inspect）
#Docker# 深入浅出
(奇淫技巧)Docker的深入浅出
25.week4 docker build 也就是创建自己的image 上传image到dockerhub 从dockerhub下载images
ASP.NET Core使用Docker-Swarm集群部署实现负载均衡实战演练

Docker 深入浅出系列 | Image 实战演练（docker image inspect）

[TOC]

Docker 已经上市很多年，不是什么新鲜事物了，很多企业或者开发同学以前也不多不少有所接触，但是有实操经验的人不多，本系列教程主要偏重实战，尽量讲干货，会根据本人理解去做阐述，具体官方概念可以查阅官方教程，因为本系列教程对前一章节有一定依赖，建议先学习前面章节内容。

本系列教程导航: Docker 深入浅出系列 | 容器初体验

课程目标

回顾 Container 与 Image 核心知识
了解如何制作自定义 Image 的两种方式
了解 Dockerfile 的一些常用指令
了解 Image 一些常用命令
了解如何基于现有 Image 创建新的 Image
了解如何运行一个 Springboot 容器

Container 与 Image 核心知识回顾

在上一篇已经提到过，Docker Image 是有多层结构，实际上由一层一层的文件系统组成，底层都是共享宿主 Linux 内核，Image 的分层结构是是为了提高复用性。Image 可以看作是 Java 的 class 文件，容器可以看成是 JAVA 的对象去理解，下层的每一层镜像可以看作是 JAVA 中的父类，上层镜像可以共享底层镜像的组件，类似 JAVA 中的继承规则。 Docker Image 基于 Union file systems 做镜像和容器分层，避免在每次以新容器运行图像时复制一组完整的文件。将更改分隔为其自身层中的容器文件系统，允许将同一容器置于从已知内容重新启动（因为在删除容器时，更改的图层将被关闭）。面向用户的是 Container 层，所有用户新增环境依赖和数据都会保存在容器层，下层 Image 只可读、不可修改。

Container 是一种轻量级的虚拟技术，不需要模拟硬件创建虚拟机启动内核空间，因此启动速度很快

Docker 是基于 Linux Kernel 的 Namespace、CGroups、UnionFileSystem 等技术封装成的一种自定义容器格式，从而提供一套虚拟运行环境。

Namespace：对全局系统资源的一种封装隔离，使得处于不同 namespace 的进程拥有独立的全局系统资源，改变一个 namespace 中的系统资源只会影响当前 namespace 里的进程，对其他 namespace 中的进程没有影响，比如 pid [进程]、net [网络]、mnt [挂载点] 等
CGroups: cgroup 和 namespace 类似，也是将进程进行分组，但它的目的和 namespace 不一样，namespace 是为了隔离进程组之间的资源，而 cgroup 是为了对一组进程进行统一的资源监控和限制，比如内存、CPU、进程数等
Union file systems：用来做 image 和 container 分层

制作 Docker Image 的两种方式

通过 Dockerfile 制作 (推荐) - Dockerfile 其内部包含了一条条的指令，每一条指令构建一层，因此每一条指令的内容，就是描述该层应当如何构建。
通过 Docker commit 操作 - 通过 docker commit 命令反向基于容器副本创建一个新的镜像文件。但是使用 docker commit 看不到 Image 的创建过程，因此对排查问题不友好。

Dockerfile 常用指令

FROM 指定基础镜像，比如 FROM centos:6 FROM centos:6
RUN 在镜像内部执行一些命令，比如安装软件，配置环境等，换行可以使用 groupadd -r mysql && useradd -r -g mysql mysql
ENV 设置变量的值，ENV MYSQL_MAJOR 5.7，可以通过 docker run --e key=value 修改，后面可以直接使用 ${MYSQL_MAJOR} ENV MYSQL_MAJOR 5.7
LABEL 设置镜像标签

LABEL email="evan08@163.com" 
LABEL name="evan"

VOLUME 定义匿名数据卷。在启动容器时忘记挂载数据卷，会自动挂载到匿名卷，在启动容器 docker run 的时候，我们可以通过 -v 参数修改挂载点。作用：
- 避免重要的数据，因容器重启而丢失，这是非常致命的。
- 避免容器不断变大。

VOLUME /var/lib/mysql

COPY 将主机的文件复制到镜像内，如果目录不存在，会自动创建所需要的目录，注意只是复制，不会提取和解压 COPY demo-api.jar /usr/loacl/app/
ADD 将主机的文件复制到镜像内，和 COPY 类似，只是 ADD 会对压缩文件提取和解压 ADD demo-api.jar /usr/loacl/app/
WORKDIR 指定镜像的工作目录，之后的命令都是基于此目录工作，若不存在则创建

WORKDIR /usr/local 
WORKDIR tomcat 
RUN touch test.txt

会在 /usr/local/tomcat 下创建 test.txt 文件

CMD 容器启动的时候默认会执行的命令，若有多个 CMD 命令，则最后一个生效

CMD ["mysqld"] 或CMD mysqld

ENTRYPOINT 和 CMD 的使用类似，但 docker run 执行时，会覆盖 CMD 的命令，而 ENTRYPOINT 不会

ENTRYPOINT ["docker-entrypoint.sh"]
ENTRYPOINT ["/bin/bash", "-C","/start.sh"]

EXPOSE 声明容器运行的服务端口，启动镜像时，可以使用 - p 将该端口映射给宿主机 EXPOSE 3306 3307

更多操作可以查看菜鸟教程

Image 实战篇

通过 Dockerfile 制作 Image

(1) 在 IDEA 创建一个 Springboot 项目 (2) 创建一个 Rest Api

@RestController
public class DemoController {

    @GetMapping("/hello")
    public String hello() {
        return "Hello";
    }


}

(3) 通过 maven 命令 mvn clean package 打包应用 target 目录会生成了一个 demo-api-0.0.1-SNAPSHOT.jar

(4) 进入上一章创建的虚拟机 Centos7 服务器中创建一个目录 demo-dockerfile 目录

使用前一章创建的密码 evan123 去登陆 Centos7 服务器

Connection to 192.168.100.9 closed.
192:centos7 evan$ ssh root@192.168.100.9
root@192.168.100.9''s password: 
Last login: Thu Jan 30 03:22:59 2020 from 192.168.100.7
-bash: warning: setlocale: LC_CTYPE: cannot change locale (UTF-8): No such file or directory
[root@10 ~]#

创建文件夹

[root@10 /]# mkdir /usr/local/demo-dockerfile

(4) 回到宿主机器，上传 demo-api-0.0.1-SNAPSHOT.jar 到 Centos7 服务器 demo-dockerfile 目录，我这里用使用命令行操作，其他童鞋可以使用其他 sfpt 工具上传

192:centos7 evan$ scp Users/evan/development/repository/eshare-docker-in-action/demo-api/target/demo-api-0.0.1-SNAPSHOT.jar  root@192.168.100.9:/usr/local/demo-dockerfile 
root@192.168.100.9''s password: 
/etc/profile.d/lang.sh: line 19: warning: setlocale: LC_CTYPE: cannot change locale (UTF-8): No such file or directory
Users/evan/development/repository/eshare-docker-in-action/demo-api/target/demo-api-0.0.1-SNAPSHOT.jar: No such file or directory
192:centos7 evan$ scp /Users/evan/development/repository/eshare-docker-in-action/demo-api/target/demo-api-0.0.1-SNAPSHOT.jar  root@192.168.100.9:/usr/local/demo-dockerfile 
root@192.168.100.9''s password: 
/etc/profile.d/lang.sh: line 19: warning: setlocale: LC_CTYPE: cannot change locale (UTF-8): No such file or directory
demo-api-0.0.1-SNAPSHOT.jar                   100%   18MB 105.8MB/s   00:00    
192:centos7 evan$

(5) 回到虚拟机，在刚才创建的目录下创建一个 Dockerfile 文件

192:centos7 evan$ ssh root@192.168.100.9
root@192.168.100.9''s password: 
Last login: Thu Jan 30 03:25:43 2020 from 192.168.100.7
-bash: warning: setlocale: LC_CTYPE: cannot change locale (UTF-8): No such file or directory
[root@10 ~]# cd /usr/local/demo-dockerfile
[root@10 demo-dockerfile]# mkdir Dockerfile
[root@10 demo-dockerfile]# touch Dockerfile
[root@10 demo-dockerfile]# ls
Dockerfile  demo-api-0.0.1-SNAPSHOT.jar

(6) 填入以下内容到 Dockerfile

FROM openjdk:8 
MAINTAINER evan 
LABEL name="demo-dockerfile" version="1.0"author="evan" COPY demo-api-0.0.1-SNAPSHOT.jar demo-api-image.jar CMD ["java","-jar","demo-api-image.jar"]

(7) 先启动 Docker 服务，假如不存在

[root@10 demo-dockerfile]# sudo systemctl start docker

(8) 在该目录下基于 Dockerfile 构建自定义的镜像

命令：docker build -t demo-api-image .

运行结果如下：

[root@10 demo-dockerfile]# docker build -t demo-api-image .
Sending build context to Docker daemon  19.32MB
Step 1/5 : FROM openjdk:8
8: Pulling from library/openjdk
146bd6a88618: Already exists 
9935d0c62ace: Already exists 
db0efb86e806: Already exists 
e705a4c4fd31: Already exists 
3d3bf7f7e874: Already exists 
49371c5b9ff6: Already exists 
3f7eaaf7ad75: Already exists 
Digest: sha256:7b7408b997615b4d6aaf6c1f0de8a32182497250288ee0a27b4e98cf14a52fb3
Status: Downloaded newer image for openjdk:8
 ---> 8c6851b1fc09
Step 2/5 : MAINTAINER evan
 ---> Running in 8fb93afccef8
Removing intermediate container 8fb93afccef8
 ---> 1f516267494a
Step 3/5 : LABEL name="demo-dockerfile" version="1.0"author="evan"
 ---> Running in 12cf6c64acf8
Removing intermediate container 12cf6c64acf8
 ---> 5ab38f113669
Step 4/5 : COPY demo-api-0.0.1-SNAPSHOT.jar demo-api-image.jar
 ---> d752dc61c8a9
Step 5/5 : CMD ["java","-jar","demo-api-image.jar"]
 ---> Running in d8bb64f014ee
Removing intermediate container d8bb64f014ee
 ---> cd026463e853
Successfully built cd026463e853
Successfully tagged demo-api-image:latest

(9) 基于我们自定义的 image 启动容器，容器命名为 demo-api

docker run -d --name demo-api -p 8999:8080 demo-api-image

(10) 查看容器的启动日志

[root@10 demo-dockerfile]# docker logs demo-api

  .   ____          _            __ _ _
 /\\ / ___''_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | ''_ | ''_| | ''_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  ''  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/
 :: Spring Boot ::        (v2.2.4.RELEASE)

2020-01-30 04:32:29.537  INFO 1 --- [           main] com.example.demo.api.DemoApiApplication  : Starting DemoApiApplication v0.0.1-SNAPSHOT on 4b90fdd0dd97 with PID 1 (/demo-api-image.jar started by root in /)
2020-01-30 04:32:29.540  INFO 1 --- [           main] com.example.demo.api.DemoApiApplication  : No active profile set, falling back to default profiles: default
2020-01-30 04:32:30.478  INFO 1 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 8080 (http)
2020-01-30 04:32:30.488  INFO 1 --- [           main] o.apache.catalina.core.StandardService   : Starting service [Tomcat]
2020-01-30 04:32:30.489  INFO 1 --- [           main] org.apache.catalina.core.StandardEngine  : Starting Servlet engine: [Apache Tomcat/9.0.30]
2020-01-30 04:32:30.540  INFO 1 --- [           main] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring embedded WebApplicationContext
2020-01-30 04:32:30.540  INFO 1 --- [           main] o.s.web.context.ContextLoader            : Root WebApplicationContext: initialization completed in 895 ms
2020-01-30 04:32:30.712  INFO 1 --- [           main] o.s.s.concurrent.ThreadPoolTaskExecutor  : Initializing ExecutorService ''applicationTaskExecutor''
2020-01-30 04:32:30.888  INFO 1 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat started on port(s): 8080 (http) with context path ''''
2020-01-30 04:32:30.890  INFO 1 --- [           main] com.example.demo.api.DemoApiApplication  : Started DemoApiApplication in 1.756 seconds (JVM running for 2.25)

(11) 在宿主机器上访问容器服务，测试 Api 是否成功部署

[root@10 demo-dockerfile]# curl localhost:8999/hello
Hello

(12) 再启动多一个容器实例测试

[root@10 demo-dockerfile]# docker run -d --name demo-api02 -p 8998:8080 demo-api-image
3029d6b4325a6773ddcacca8d39917b1abfe12d6004cc8a765608f7f2d64edb3
[root@10 demo-dockerfile]# curl localhost:8998/hello
Hello

(12) 登陆 Docker 镜像仓库，没有账号的童鞋提前到 hub.docker.com 注册

[root@10 demo-dockerfile]# docker login
Login with your Docker ID to push and pull images from Docker Hub. If you don''t have a Docker ID, head over to https://hub.docker.com to create one.
Username: 10856214
Password: 
WARNING! Your password will be stored unencrypted in /root/.docker/config.json.
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credentials-store

Login Succeeded

(13) 推送定制的 Docker 镜像到远程仓库，镜像名称要跟 Docker id 一致

[root@10 demo-dockerfile]# docker tag demo-api-image 10856214/demo-api-image
[root@10 demo-dockerfile]# docker push 10856214/demo-api-image
The push refers to repository [docker.io/10856214/demo-api-image]
9fb0d7d193ef: Pushed 
a6ded049566a: Mounted from library/openjdk 
e7fe5541de5f: Mounted from library/openjdk 
03ff63c55220: Mounted from library/openjdk 
bee1e39d7c3a: Mounted from library/openjdk 
1f59a4b2e206: Mounted from library/openjdk 
0ca7f54856c0: Mounted from library/openjdk 
ebb9ae013834: Mounted from library/openjdk 
latest: digest: sha256:32afd9d8ca8205d6e667543a66163330c5067c5a37ebd80d53e9563b809e8bb4 size: 2007

(14) 查看 Image 是否已经成功推送到远程仓库

(15) 从远程仓库把 Image 拉到本地

[root@10 demo-dockerfile]# docker pull 10856214/demo-api-image
Using default tag: latest
latest: Pulling from 10856214/demo-api-image
Digest: sha256:32afd9d8ca8205d6e667543a66163330c5067c5a37ebd80d53e9563b809e8bb4
Status: Image is up to date for 10856214/demo-api-image:latest
docker.io/10856214/demo-api-image:latest

(16) 基于远程 10856214/demo-api-image 启动容器

[root@10 demo-dockerfile]# docker run -d --name demo-api03 -p 8997:8080 10856214/demo-api-image
f6907cc3f8b7c21e26111c748de23d923f96f5b2ffef54478ff49d8c03416651
[root@10 demo-dockerfile]# docker ps
CONTAINER ID        IMAGE                     COMMAND                  CREATED             STATUS              PORTS                    NAMES
f6907cc3f8b7        10856214/demo-api-image   "java -jar demo-api-…"   4 seconds ago       Up 3 seconds        0.0.0.0:8997->8080/tcp   demo-api03
3029d6b4325a        demo-api-image            "java -jar demo-api-…"   About an hour ago   Up About an hour    0.0.0.0:8998->8080/tcp   demo-api02
4b90fdd0dd97        demo-api-image            "java -jar demo-api-…"   About an hour ago   Up About an hour    0.0.0.0:8999->8080/tcp   demo-api
[root@10 demo-dockerfile]#

通过 Docker Commit 创建 Image

(1) 查看运行中的容器

[root@10 demo-dockerfile]# docker ps
CONTAINER ID        IMAGE                     COMMAND                  CREATED             STATUS              PORTS                    NAMES
f6907cc3f8b7        10856214/demo-api-image   "java -jar demo-api-…"   2 hours ago         Up 2 hours          0.0.0.0:8997->8080/tcp   demo-api03
3029d6b4325a        demo-api-image            "java -jar demo-api-…"   3 hours ago         Up 3 hours          0.0.0.0:8998->8080/tcp   demo-api02
4b90fdd0dd97        demo-api-image            "java -jar demo-api-…"   3 hours ago         Up 3 hours          0.0.0.0:8999->8080/tcp   demo-api
[root@10 demo-dockerfile]#

(2) 进入我们在上一节从远程仓库拉回来的自定义镜像内部

[root@10 demo-dockerfile]# docker exec -it demo-api03 bash
root@f6907cc3f8b7:/#

(3) 修改容器 demo-api03, 在容器内部安装 yum 工具

尝试运行 yum 指令，默认是不带 yum 工具，因为容器里的 linux 操作系统只保留基本指令

root@f6907cc3f8b7:/# yum
bash: yum: command not found
root@f6907cc3f8b7:/#

查看下容器内部的 linux 操作系统版本

root@f6907cc3f8b7:/# cat /etc/issue
Debian GNU/Linux 9 \n \l

内置的操作系统用的 Debian

使用 apt-get 更新系统组件

root@f6907cc3f8b7:/# apt-get update
Ign:1 http://deb.debian.org/debian stretch InRelease
Get:2 http://security.debian.org/debian-security stretch/updates InRelease [94.3 kB]
Get:3 http://deb.debian.org/debian stretch-updates InRelease [91.0 kB]
Get:4 http://deb.debian.org/debian stretch Release [118 kB]              
Get:5 http://security.debian.org/debian-security stretch/updates/main amd64 Packages [516 kB]
Get:6 http://deb.debian.org/debian stretch-updates/main amd64 Packages [27.9 kB]
Get:7 http://deb.debian.org/debian stretch Release.gpg [2365 B]               
Get:8 http://deb.debian.org/debian stretch/main amd64 Packages [7086 kB]
Fetched 7936 kB in 1min 18s (101 kB/s)                                         
Reading package lists... Done

安装容器内置操作系统必要依赖

apt-get install build-essential

下载安装 yum 组件

apt-get install yum

测试 yum 是否安装成功

root@f6907cc3f8b7:/# yum --help
Usage: yum [options] COMMAND

List of Commands:

check          Check for problems in the rpmdb
check-update   Check for available package updates
clean          Remove cached data
deplist        List a package''s dependencies
...

(4) 通过以上步骤，我们已经成功修改了容器，接下来我们推出容器，基于当前容器版本创建一个新的 Image, 命名为 demo-api-image-v1

[root@10 demo-dockerfile]# docker commit demo-api03 demo-api-image-v1
sha256:7887668690a3e53c27535669252f67b0391d54443776f1a431f91fe5800958be
[root@10 demo-dockerfile]#

这时候创建出来的 Image 是默认已经携带了 yum 组件

(5) 基于上面更新的新镜像 demo-api-image-v1 创建一个容器

[root@10 demo-dockerfile]# docker run -d -it --name demo-api-v1 demo-api-image-v1
6363450e8f7af1f53f935e345d50f7bbfd3ff82bb2409fd5fd75a0f253ed1de8

(6) 进入 demo-api-v2 容器验证是否已经存在 yum 组件

[root@10 demo-dockerfile]# docker exec -it demo-api-v1 bash
root@6363450e8f7a:/# yum
You need to give some command
Usage: yum [options] COMMAND

List of Commands:

check          Check for problems in the rpmdb
check-update   Check for available package updates
clean          Remove cached data
deplist        List a package''s dependencie
...

附录

Image 常用操作

查看本地 image 列表 docker images docker image ls
获取远端镜像 docker pull
删除镜像 [注意此镜像如果正在使用，或者有关联的镜像，则需要先处理完] docker image rm imageid docker rmi -f imageid docker rmi -f $(docker image ls) 删除所有镜像
运行镜像 docker run image
发布镜像 docker push

Container 常用操作

根据镜像创建容器 docker run -d --name -p 9090:8080 my-tomcat tomcat
查看运行中的 container docker ps
查看所有的 container [包含退出的] docker ps -a
删除 container docker rm containerid docker rm -f $(docker ps -a) 删除所有 container
进入到一个 container 中 docker exec -it container bash
根据 container 生成 image docker commit demo-api03 demo-api-image-v1
查看某个 container 的日志 docker logs container
查看容器资源使用情况 docker stats
查看容器详情信息 docker inspect container
停止 / 启动容器 docker stop/start container

项目 Demo Github

https://github.com/EvanLeung08/eshare-docker-in-action.git

有兴趣的朋友，欢迎加我公众号一起交流，有问题可以留言，平时工作比较忙，我也抽时间尽量回复每位朋友的留言，谢谢！

#Docker# 深入浅出

参考内容在：

http://www.infoq.com/cn/articles/docker-command-line-quest

http://www.infoq.com/cn/articles/docker-core-technology-preview

(奇淫技巧)Docker的深入浅出

docker是什么

这里用简单的几句话描述docker做了什么事情。

docker是一个可以创建、管理容器的东西。可以理解为docker里面存放了许多容器。

容器就是一个精简版的linux系统，这个系统只有基本的环境供以使用，里面可以运行程序(可以是MysqL，可以是Nginx，可以是redis等)。

容器的创建是依赖于镜像的，镜像可以看作是一个模板，docker可以根据镜像生成一个容器实例，假如你需要一个容器中放入MysqL，那么就去docker的镜像仓库拉取一个MysqL镜像(可指定版本)，然后docker可以基于这个镜像创建一个MysqL容器，这样就能在docker中运行使用一个只含有MysqL的系统了。

容器的存在使我们可以方便做很多事情，比如项目需要MysqL、Nginx环境来运行，可以直接创建MysqL和Nginx容器供项目使用，不需要在服务器上下载、安装、配置这些环境，容器内部已经包含了这些必备的东西。同时容器还可以很方便的移植，比如我们需要切换服务器，这些项目正在使用的容器可以直接打包带走放在另一个服务器上。

定义：

Docker是一个虚拟环境容器，可以将你的开发环境、代码、配置文件等一并打包到这个容器中，并发布和应用到任意平台中。原理： docker底层使用了LXC来实现，LXC将linux进程沙盒化，使得进程之间相互隔离，并且能够协调各进程的资源分配。 LXC： LXC为Linux Container的简写。可以提供轻量级的虚拟化，以便隔离进程和资源，而且不需要提供指令解释机制以及全虚拟化的其他复杂性。

Docker三个重要概念：

镜像（Image）：类似于虚拟机中的镜像，是一个包含有文件系统的面向Docker引擎的只读模板。任何应用程序运行都需要环境，而镜像就是用来提供这种运行环境的。容器（Container）：类似于一个轻量级的沙盒，可以将其看作一个极简的Linux系统环境（包括root权限、进程空间、用户空间和网络空间等），以及运行在其中的应用程序。Docker引擎利用容器来运行、隔离各个应用。容器是镜像创建的应用实例，可以创建、启动、停止、删除容器，各个容器之间是是相互隔离的，互不影响。注意：镜像本身是只读的，容器从镜像启动时，Docker在镜像的上层创建一个可写层，镜像本身不变。仓库（Repository）：类似于代码仓库，这里是镜像仓库，是Docker用来集中存放镜像文件的地方。注意与注册服务器（Registry）的区别：注册服务器是存放仓库的地方，一般会有多个仓库；而仓库是存放镜像的地方，一般每个仓库存放一类镜像，每个镜像利用tag进行区分。

容器和虚拟机的区别：

容器是应用程序层的抽象，将代码和依赖项打包在一起。多个容器可以在同一台计算机上运行，并与其他容器共享OS内核，每个容器在用户空间中作为隔离的进程运行。容器占用的空间少于VM（容器映像的大小通常为几十MB），可以处理更多的应用程序，并且需要的VM和操作系统更少。

虚拟机（VM）是将一台服务器转变为多台服务器的物理硬件的抽象。系统管理程序允许多个VM在单台计算机上运行。每个VM包含操作系统，应用程序，必要的二进制文件和库的完整副本-占用数十GB。VM也可能启动缓慢。

Docker 简化了环境配置流程

Docker 使用的技术几乎没有新技术，大多是对 Linux 已经存在的技术的封装。Docker 中的容器，是使用 Linux 之前的一些技术，把开发需要设置的环境，全部隔离在一起，形成一个集装箱。当有其他的环境需要配置的时候，只需要复制一个集装箱就可以了。

容器可以轻松创建和销毁

在环境配置的时候，还可以使用创建虚拟机的方式来实现环境同步。如果服务器用的是 centos 的系统，可以在开发的时候就用 centos 开发。这确实解决了一些问题，但是还是需要去独立配置每一台机器。而且，虚拟机本身对多个程序之间的环境不兼容的时候无能为力，可能需要借助第三方的一些管理工具，而 Docker 却可以轻松在一台机器上运行多个容器。

Docker 容器和虚拟机

容器不是一台机器。Docker 利用的是 Linux 的资源分离机制，例如 cgroups，以及 Linux 核心命名空间（namespaces），来建立独立的容器（containers）。容器看上去是一台机器，实际上是一个进程。

相比于虚拟机，容器的优势主要有：

资源占用少
启动速度快
本身体积小

Docker 给软件开发领域带来的不仅仅是提供环境，可以说它直接带火了 Golang。因为 Docker 容器创建和销毁非常方便，很适合用来动态扩容和缩容，可以直接用在云计算当中的弹性服务当中。另外，基于 Docker 容器的隔离特性，一台服务器上可以同时跑很多个程序而做到管理方便，很符合微服务架构的需要。

k8s与Docker的关系

1、K8S是用来管理容器的，pod是k8s的最小操作单位。pod包含各个功能的容器，pod在node运行，master管理node。

2、Docker就是创建容器的工具，可以看作k8s的组件。

优点：

1.部署方便 2.部署安全 3.隔离性 4.快速回滚 5.资源利用率高 6.管理成本低

缺点：

1.隔离性 2.性能（数据交互，网络连接） 3.复杂

Docker中各容器如何通信（推荐使用）：

docker network来创建一个桥接网络，在docker run的时候将容器指定到新创建的桥接网络中，这样同一桥接网络中的容器就可以通过互相访问。创建网络： docker network create test-network 启动容器时，加入创建的网络： docker run -it --network test-network --network-alias MysqL -e MysqL_ROOT_PASSWORD=123 MysqL:5.7 启动被链接的容器： docker run -it --network test-network --network-alias centos centos /bin/bash

Docker安装

要求：lunix内核，要求3.8以上 1.安装工具包：

2.设置远程仓库：

3.安装docker：

4.启动docker：

5.查看版本：

6.校验：

看到这行没关系，稍等一下就好了

25.week4 docker build 也就是创建自己的image 上传image到dockerhub 从dockerhub下载images

dado可以写你自己的名字

这个命令就会根据目录下的Dockerfile（固定用和这个名字）文件里面的内容去下载并创建运行命令一步一步地

Setting up libxfixes3:amd64 (1:5.0.1-2) ...
Setting up libxinerama1:amd64 (2:1.1.3-1) ...
Setting up libxshmfence1:amd64 (1.2-1) ...
Setting up libxtst6:amd64 (2:1.2.2-1) ...
Setting up libxxf86vm1:amd64 (1:1.1.4-1) ...
Setting up libjbig0:amd64 (2.1-3.1) ...
Setting up libtxc-dxtn-s2tc0:amd64 (0~git20131104-1.1) ...
update-alternatives: using /usr/lib/x86_64-linux-gnu/libtxc_dxtn_s2tc.so.0 to provide /usr/lib/x86_64-linux-gnu/libtxc_dxtn.so (libtxc-dxtn-x86_64-linux-gnu) in auto mode
Setting up libbsd0:amd64 (0.8.2-1) ...
Setting up libnettle6:amd64 (3.2-1ubuntu0.16.04.1) ...
Setting up libhogweed4:amd64 (3.2-1ubuntu0.16.04.1) ...
Setting up libidn11:amd64 (1.32-3ubuntu1.2) ...
Setting up libp11-kit0:amd64 (0.23.2-5~ubuntu16.04.1) ...
Setting up libtasn1-6:amd64 (4.7-3ubuntu0.16.04.3) ...
Setting up libgnutls30:amd64 (3.4.10-4ubuntu1.4) ...
Setting up libsqlite3-0:amd64 (3.11.0-1ubuntu1) ...
Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu4.13) ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (Can''t locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.22.1 /usr/local/share/perl/5.22.1 /usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7.)
debconf: falling back to frontend: Teletype
Setting up openssl (1.0.2g-1ubuntu4.13) ...
Setting up ca-certificates (20170717~16.04.1) ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (Can''t locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.22.1 /usr/local/share/perl/5.22.1 /usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7.)
debconf: falling back to frontend: Teletype
Setting up libcap-ng0:amd64 (0.7.7-1) ...
Setting up libdbus-1-3:amd64 (1.10.6-1ubuntu3.3) ...
Setting up dbus (1.10.6-1ubuntu3.3) ...
Setting up krb5-locales (1.13.2+dfsg-5ubuntu2) ...
Setting up libdrm-common (2.4.91-2~16.04.1) ...
Setting up libdrm2:amd64 (2.4.91-2~16.04.1) ...
Setting up libedit2:amd64 (3.1-20150325-1ubuntu2) ...
Setting up libelf1:amd64 (0.165-3ubuntu1.1) ...
Setting up libglib2.0-data (2.48.2-0ubuntu4) ...
Setting up libkrb5support0:amd64 (1.13.2+dfsg-5ubuntu2) ...
Setting up libk5crypto3:amd64 (1.13.2+dfsg-5ubuntu2) ...
Setting up libkeyutils1:amd64 (1.5.9-8ubuntu1) ...
Setting up libkrb5-3:amd64 (1.13.2+dfsg-5ubuntu2) ...
Setting up libgssapi-krb5-2:amd64 (1.13.2+dfsg-5ubuntu2) ...
Setting up libicu55:amd64 (55.1-7ubuntu0.4) ...
Setting up libxml2:amd64 (2.9.3+dfsg1-1ubuntu0.6) ...
Setting up shared-mime-info (1.5-2ubuntu0.2) ...
Setting up xdg-user-dirs (0.15-2ubuntu6.16.04.1) ...
Setting up xml-core (0.13+nmu2) ...
Setting up java-common (0.56ubuntu2) ...
Setting up libavahi-common-data:amd64 (0.6.32~rc+dfsg-1ubuntu2.2) ...
Setting up libavahi-common3:amd64 (0.6.32~rc+dfsg-1ubuntu2.2) ...
Setting up libavahi-client3:amd64 (0.6.32~rc+dfsg-1ubuntu2.2) ...
Setting up libcups2:amd64 (2.1.3-4ubuntu0.5) ...
Setting up libjpeg8:amd64 (8c-2ubuntu8) ...
Setting up libnspr4:amd64 (2:4.13.1-0ubuntu0.16.04.1) ...
Setting up libpcsclite1:amd64 (1.8.14-1ubuntu1.16.04.1) ...
Setting up libxi6:amd64 (2:1.7.6-1) ...
Setting up libxrender1:amd64 (1:0.9.9-0ubuntu1) ...
Setting up fonts-dejavu-extra (2.35-1) ...
Setting up hicolor-icon-theme (0.15-0ubuntu1.1) ...
Setting up libasound2-data (1.1.0-0ubuntu1) ...
Setting up libasound2:amd64 (1.1.0-0ubuntu1) ...
Setting up libatk1.0-data (2.18.0-1) ...
Setting up libatk1.0-0:amd64 (2.18.0-1) ...
Setting up libpixman-1-0:amd64 (0.33.6-1) ...
Setting up libxcb-render0:amd64 (1.11.1-1ubuntu1) ...
Setting up libxcb-shm0:amd64 (1.11.1-1ubuntu1) ...
Setting up libcairo2:amd64 (1.14.6-1) ...
Setting up libdatrie1:amd64 (0.2.10-2) ...
Setting up libdrm-amdgpu1:amd64 (2.4.91-2~16.04.1) ...
Setting up libpciaccess0:amd64 (0.13.4-1) ...
Setting up libdrm-intel1:amd64 (2.4.91-2~16.04.1) ...
Setting up libdrm-nouveau2:amd64 (2.4.91-2~16.04.1) ...
Setting up libdrm-radeon1:amd64 (2.4.91-2~16.04.1) ...
Setting up libflac8:amd64 (1.3.1-4) ...
Setting up libtiff5:amd64 (4.0.6-1ubuntu0.4) ...
Setting up libgdk-pixbuf2.0-common (2.32.2-1ubuntu1.5) ...
Setting up libgdk-pixbuf2.0-0:amd64 (2.32.2-1ubuntu1.5) ...
Setting up libgif7:amd64 (5.1.4-0.3~16.04) ...
Setting up libglapi-mesa:amd64 (18.0.5-0ubuntu0~16.04.1) ...
Setting up libllvm6.0:amd64 (1:6.0-1ubuntu2~16.04.1) ...
Setting up libsensors4:amd64 (1:3.4.0-2) ...
Setting up libgl1-mesa-dri:amd64 (18.0.5-0ubuntu0~16.04.1) ...
Setting up libx11-xcb1:amd64 (2:1.6.3-1ubuntu2) ...
Setting up libxcb-dri2-0:amd64 (1.11.1-1ubuntu1) ...
Setting up libxcb-dri3-0:amd64 (1.11.1-1ubuntu1) ...
Setting up libxcb-glx0:amd64 (1.11.1-1ubuntu1) ...
Setting up libxcb-present0:amd64 (1.11.1-1ubuntu1) ...
Setting up libxcb-sync1:amd64 (1.11.1-1ubuntu1) ...
Setting up libgl1-mesa-glx:amd64 (18.0.5-0ubuntu0~16.04.1) ...
update-alternatives: using /usr/lib/x86_64-linux-gnu/mesa/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in auto mode
Setting up libgraphite2-3:amd64 (1.3.10-0ubuntu0.16.04.1) ...
Setting up libgtk2.0-common (2.24.30-1ubuntu1.16.04.2) ...
Setting up libthai-data (0.1.24-2) ...
Setting up libthai0:amd64 (0.1.24-2) ...
Setting up libpango-1.0-0:amd64 (1.38.1-1) ...
Setting up libharfbuzz0b:amd64 (1.0.1-1ubuntu0.1) ...
Setting up libpangoft2-1.0-0:amd64 (1.38.1-1) ...
Setting up libpangocairo-1.0-0:amd64 (1.38.1-1) ...
Setting up libxcursor1:amd64 (1:1.1.14-1ubuntu0.16.04.2) ...
Setting up libxrandr2:amd64 (2:1.5.0-1) ...
Setting up libgtk2.0-0:amd64 (2.24.30-1ubuntu1.16.04.2) ...
Setting up libgtk2.0-bin (2.24.30-1ubuntu1.16.04.2) ...
Setting up xorg-sgml-doctools (1:1.11-1) ...
Setting up x11proto-core-dev (7.0.31-1~ubuntu16.04.2) ...
Setting up libice-dev:amd64 (2:1.0.9-1) ...
Setting up libpthread-stubs0-dev:amd64 (0.3-4) ...
Setting up libvorbis0a:amd64 (1.3.5-3ubuntu0.2) ...
Setting up libvorbisenc2:amd64 (1.3.5-3ubuntu0.2) ...
Setting up libsndfile1:amd64 (1.0.25-10ubuntu0.16.04.1) ...
Setting up libpulse0:amd64 (1:8.0-0ubuntu3.10) ...
Setting up libsm-dev:amd64 (2:1.2.2-1) ...
Setting up libxau-dev:amd64 (1:1.0.8-1) ...
Setting up libxdmcp-dev:amd64 (1:1.1.2-1.1) ...
Setting up x11proto-input-dev (2.3.1-1) ...
Setting up x11proto-kb-dev (1.0.7-0ubuntu1) ...
Setting up xtrans-dev (1.3.5-1) ...
Setting up libxcb1-dev:amd64 (1.11.1-1ubuntu1) ...
Setting up libx11-dev:amd64 (2:1.6.3-1ubuntu2) ...
Setting up libx11-doc (2:1.6.3-1ubuntu2) ...
Setting up libxt6:amd64 (1:1.1.5-0ubuntu1) ...
Setting up libxt-dev:amd64 (1:1.1.5-0ubuntu1) ...
Setting up tcpd (7.6.q-25) ...
Setting up libnss3-nssdb (2:3.28.4-0ubuntu0.16.04.3) ...
Setting up libnss3:amd64 (2:3.28.4-0ubuntu0.16.04.3) ...
Setting up openjdk-8-jre-headless:amd64 (8u181-b13-0ubuntu0.16.04.1) ...
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/rmid to provide /usr/bin/rmid (rmid) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java to provide /usr/bin/java (java) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/keytool to provide /usr/bin/keytool (keytool) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/jjs to provide /usr/bin/jjs (jjs) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/pack200 to provide /usr/bin/pack200 (pack200) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/rmiregistry to provide /usr/bin/rmiregistry (rmiregistry) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/unpack200 to provide /usr/bin/unpack200 (unpack200) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/orbd to provide /usr/bin/orbd (orbd) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/servertool to provide /usr/bin/servertool (servertool) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/tnameserv to provide /usr/bin/tnameserv (tnameserv) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/jexec to provide /usr/bin/jexec (jexec) in auto mode
Setting up ca-certificates-java (20160321ubuntu1) ...
done.
Setting up openjdk-8-jre:amd64 (8u181-b13-0ubuntu0.16.04.1) ...
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/policytool to provide /usr/bin/policytool (policytool) in auto mode
Setting up openjdk-8-jdk-headless:amd64 (8u181-b13-0ubuntu0.16.04.1) ...
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/idlj to provide /usr/bin/idlj (idlj) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jdeps to provide /usr/bin/jdeps (jdeps) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/wsimport to provide /usr/bin/wsimport (wsimport) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/rmic to provide /usr/bin/rmic (rmic) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jinfo to provide /usr/bin/jinfo (jinfo) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jsadebugd to provide /usr/bin/jsadebugd (jsadebugd) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/native2ascii to provide /usr/bin/native2ascii (native2ascii) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jstat to provide /usr/bin/jstat (jstat) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javac to provide /usr/bin/javac (javac) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javah to provide /usr/bin/javah (javah) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jps to provide /usr/bin/jps (jps) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jstack to provide /usr/bin/jstack (jstack) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jrunscript to provide /usr/bin/jrunscript (jrunscript) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javadoc to provide /usr/bin/javadoc (javadoc) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jhat to provide /usr/bin/jhat (jhat) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javap to provide /usr/bin/javap (javap) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jar to provide /usr/bin/jar (jar) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/extcheck to provide /usr/bin/extcheck (extcheck) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/schemagen to provide /usr/bin/schemagen (schemagen) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/xjc to provide /usr/bin/xjc (xjc) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jmap to provide /usr/bin/jmap (jmap) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jstatd to provide /usr/bin/jstatd (jstatd) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jdb to provide /usr/bin/jdb (jdb) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/serialver to provide /usr/bin/serialver (serialver) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/wsgen to provide /usr/bin/wsgen (wsgen) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jcmd to provide /usr/bin/jcmd (jcmd) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jarsigner to provide /usr/bin/jarsigner (jarsigner) in auto mode
Setting up openjdk-8-jdk:amd64 (8u181-b13-0ubuntu0.16.04.1) ...
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/appletviewer to provide /usr/bin/appletviewer (appletviewer) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jconsole to provide /usr/bin/jconsole (jconsole) in auto mode
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Processing triggers for systemd (229-4ubuntu21.2) ...
Processing triggers for ca-certificates (20170717~16.04.1) ...
Updating certificates in /etc/ssl/certs...
148 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...

Adding debian:ACCVRAIZ1.pem
Adding debian:ACEDICOM_Root.pem
Adding debian:AC_RAIZ_FNMT-RCM.pem
Adding debian:Actalis_Authentication_Root_CA.pem
Adding debian:AddTrust_External_Root.pem
Adding debian:AddTrust_Low-Value_Services_Root.pem
Adding debian:AddTrust_Public_Services_Root.pem
Adding debian:AddTrust_Qualified_Certificates_Root.pem
Adding debian:AffirmTrust_Commercial.pem
Adding debian:AffirmTrust_Networking.pem
Adding debian:AffirmTrust_Premium.pem
Adding debian:AffirmTrust_Premium_ECC.pem
Adding debian:Amazon_Root_CA_1.pem
Adding debian:Amazon_Root_CA_2.pem
Adding debian:Amazon_Root_CA_3.pem
Adding debian:Amazon_Root_CA_4.pem
Adding debian:Atos_TrustedRoot_2011.pem
Adding debian:Autoridad_de_Certificacion_Firmaprofesional_CIF_A62634068.pem
Adding debian:Baltimore_CyberTrust_Root.pem
Adding debian:Buypass_Class_2_Root_CA.pem
Adding debian:Buypass_Class_3_Root_CA.pem
Adding debian:CA_Disig_Root_R1.pem
Adding debian:CA_Disig_Root_R2.pem
Adding debian:CFCA_EV_ROOT.pem
Adding debian:CNNIC_ROOT.pem
Adding debian:COMODO_Certification_Authority.pem
Adding debian:COMODO_ECC_Certification_Authority.pem
Adding debian:COMODO_RSA_Certification_Authority.pem
Adding debian:Camerfirma_Chambers_of_Commerce_Root.pem
Adding debian:Camerfirma_Global_Chambersign_Root.pem
Adding debian:Certigna.pem
Adding debian:Certinomis_-_Autorité_Racine.pem
Adding debian:Certinomis_-_Root_CA.pem
Adding debian:Certplus_Class_2_Primary_CA.pem
Adding debian:Certplus_Root_CA_G1.pem
Adding debian:Certplus_Root_CA_G2.pem
Adding debian:Certum_Root_CA.pem
Adding debian:Certum_Trusted_Network_CA.pem
Adding debian:Certum_Trusted_Network_CA_2.pem
Adding debian:Chambers_of_Commerce_Root_-_2008.pem
Adding debian:China_Internet_Network_Information_Center_EV_Certificates_Root.pem
Adding debian:Comodo_AAA_Services_root.pem
Adding debian:Comodo_Secure_Services_root.pem
Adding debian:Comodo_Trusted_Services_root.pem
Adding debian:Cybertrust_Global_Root.pem
Adding debian:D-TRUST_Root_Class_3_CA_2_2009.pem
Adding debian:D-TRUST_Root_Class_3_CA_2_EV_2009.pem
Adding debian:DST_ACES_CA_X6.pem
Adding debian:DST_Root_CA_X3.pem
Adding debian:Deutsche_Telekom_Root_CA_2.pem
Adding debian:DigiCert_Assured_ID_Root_CA.pem
Adding debian:DigiCert_Assured_ID_Root_G2.pem
Adding debian:DigiCert_Assured_ID_Root_G3.pem
Adding debian:DigiCert_Global_Root_CA.pem
Adding debian:DigiCert_Global_Root_G2.pem
Adding debian:DigiCert_Global_Root_G3.pem
Adding debian:DigiCert_High_Assurance_EV_Root_CA.pem
Adding debian:DigiCert_Trusted_Root_G4.pem
Adding debian:E-Tugra_Certification_Authority.pem
Adding debian:EC-ACC.pem
Adding debian:EE_Certification_Centre_Root_CA.pem
Adding debian:Entrust.net_Premium_2048_Secure_Server_CA.pem
Adding debian:Entrust_Root_Certification_Authority.pem
Adding debian:Entrust_Root_Certification_Authority_-_EC1.pem
Adding debian:Entrust_Root_Certification_Authority_-_G2.pem
Adding debian:GeoTrust_Global_CA.pem
Adding debian:GeoTrust_Global_CA_2.pem
Adding debian:GeoTrust_Primary_Certification_Authority.pem
Adding debian:GeoTrust_Primary_Certification_Authority_-_G2.pem
Adding debian:GeoTrust_Primary_Certification_Authority_-_G3.pem
Adding debian:GeoTrust_Universal_CA.pem
Adding debian:GeoTrust_Universal_CA_2.pem
Adding debian:GlobalSign_ECC_Root_CA_-_R4.pem
Adding debian:GlobalSign_ECC_Root_CA_-_R5.pem
Adding debian:GlobalSign_Root_CA.pem
Adding debian:GlobalSign_Root_CA_-_R2.pem
Adding debian:GlobalSign_Root_CA_-_R3.pem
Adding debian:Global_Chambersign_Root_-_2008.pem
Adding debian:Go_Daddy_Class_2_CA.pem
Adding debian:Go_Daddy_Root_Certificate_Authority_-_G2.pem
Adding debian:Hellenic_Academic_and_Research_Institutions_ECC_RootCA_2015.pem
Adding debian:Hellenic_Academic_and_Research_Institutions_RootCA_2011.pem
Adding debian:Hellenic_Academic_and_Research_Institutions_RootCA_2015.pem
Adding debian:Hongkong_Post_Root_CA_1.pem
Adding debian:ISRG_Root_X1.pem
Adding debian:IdenTrust_Commercial_Root_CA_1.pem
Adding debian:IdenTrust_Public_Sector_Root_CA_1.pem
Adding debian:Izenpe.com.pem
Adding debian:LuxTrust_Global_Root_2.pem
Adding debian:Microsec_e-Szigno_Root_CA_2009.pem
Adding debian:NetLock_Arany_=Class_Gold=_Főtanúsítvány.pem
Adding debian:Network_Solutions_Certificate_Authority.pem
Adding debian:OISTE_WISeKey_Global_Root_GA_CA.pem
Adding debian:OISTE_WISeKey_Global_Root_GB_CA.pem
Adding debian:OpenTrust_Root_CA_G1.pem
Adding debian:OpenTrust_Root_CA_G2.pem
Adding debian:OpenTrust_Root_CA_G3.pem
Adding debian:PSCProcert.pem
Adding debian:QuoVadis_Root_CA.pem
Adding debian:QuoVadis_Root_CA_1_G3.pem
Adding debian:QuoVadis_Root_CA_2.pem
Adding debian:QuoVadis_Root_CA_2_G3.pem
Adding debian:QuoVadis_Root_CA_3.pem
Adding debian:QuoVadis_Root_CA_3_G3.pem
Adding debian:SZAFIR_ROOT_CA2.pem
Adding debian:SecureSign_RootCA11.pem
Adding debian:SecureTrust_CA.pem
Adding debian:Secure_Global_CA.pem
Adding debian:Security_Communication_EV_RootCA1.pem
Adding debian:Security_Communication_RootCA2.pem
Adding debian:Security_Communication_Root_CA.pem
Adding debian:Sonera_Class_2_Root_CA.pem
Adding debian:Staat_der_Nederlanden_EV_Root_CA.pem
Adding debian:Staat_der_Nederlanden_Root_CA_-_G2.pem
Adding debian:Staat_der_Nederlanden_Root_CA_-_G3.pem
Adding debian:Starfield_Class_2_CA.pem
Adding debian:Starfield_Root_Certificate_Authority_-_G2.pem
Adding debian:Starfield_Services_Root_Certificate_Authority_-_G2.pem
Adding debian:SwissSign_Gold_CA_-_G2.pem
Adding debian:SwissSign_Silver_CA_-_G2.pem
Adding debian:Swisscom_Root_CA_1.pem
Adding debian:Swisscom_Root_CA_2.pem
Adding debian:Swisscom_Root_EV_CA_2.pem
Adding debian:T-TeleSec_GlobalRoot_Class_2.pem
Adding debian:T-TeleSec_GlobalRoot_Class_3.pem
Adding debian:TUBITAK_Kamu_SM_SSL_Kok_Sertifikasi_-_Surum_1.pem
Adding debian:TURKTRUST_Certificate_Services_Provider_Root_2007.pem
Adding debian:TWCA_Global_Root_CA.pem
Adding debian:TWCA_Root_Certification_Authority.pem
Adding debian:Taiwan_GRCA.pem
Adding debian:TeliaSonera_Root_CA_v1.pem
Adding debian:Trustis_FPS_Root_CA.pem
Adding debian:TÜBİTAK_UEKAE_Kök_Sertifika_Hizmet_Sağlayıcısı_-_Sürüm_3.pem
Adding debian:TÜRKTRUST_Elektronik_Sertifika_Hizmet_Sağlayıcısı_H5.pem
Adding debian:USERTrust_ECC_Certification_Authority.pem
Adding debian:USERTrust_RSA_Certification_Authority.pem
Adding debian:UTN_USERFirst_Hardware_Root_CA.pem
Adding debian:VeriSign_Class_3_Public_Primary_Certification_Authority_-_G4.pem
Adding debian:VeriSign_Class_3_Public_Primary_Certification_Authority_-_G5.pem
Adding debian:VeriSign_Universal_Root_Certification_Authority.pem
Adding debian:Verisign_Class_3_Public_Primary_Certification_Authority_-_G3.pem
Adding debian:Visa_eCommerce_Root.pem
Adding debian:XRamp_Global_CA_Root.pem
Adding debian:certSIGN_ROOT_CA.pem
Adding debian:ePKI_Root_Certification_Authority.pem
Adding debian:thawte_Primary_Root_CA.pem
Adding debian:thawte_Primary_Root_CA_-_G2.pem
Adding debian:thawte_Primary_Root_CA_-_G3.pem
done.
done.
Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
Removing intermediate container 0f23a95bea42
 ---> 8f93746ccfe5
Step 7/7 : RUN apt-get install -y python
 ---> Running in fc2aeb8c23dd
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  file libmagic1 libpython-stdlib libpython2.7-minimal libpython2.7-stdlib
  mime-support python-minimal python2.7 python2.7-minimal
Suggested packages:
  python-doc python-tk python2.7-doc binfmt-support
The following NEW packages will be installed:
  file libmagic1 libpython-stdlib libpython2.7-minimal libpython2.7-stdlib
  mime-support python python-minimal python2.7 python2.7-minimal
0 upgraded, 10 newly installed, 0 to remove and 6 not upgraded.
Need to get 4145 kB of archives.
After this operation, 20.9 MB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libpython2.7-minimal amd64 2.7.12-1ubuntu0~16.04.3 [340 kB]
Get:2 http://101.44.1.125/files/B067000006FC9787/ubuntu.cn99.com/ubuntu xenial-updates/main amd64 python2.7-minimal amd64 2.7.12-1ubuntu0~16.04.3 [1261 kB]
Get:3 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 python-minimal amd64 2.7.12-1~16.04 [28.1 kB]
Get:4 http://archive.ubuntu.com/ubuntu xenial/main amd64 mime-support all 3.59ubuntu1 [31.0 kB]
Get:5 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libpython2.7-stdlib amd64 2.7.12-1ubuntu0~16.04.3 [1880 kB]
Get:6 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 python2.7 amd64 2.7.12-1ubuntu0~16.04.3 [224 kB]
Get:7 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libpython-stdlib amd64 2.7.12-1~16.04 [7768 B]
Get:8 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 python amd64 2.7.12-1~16.04 [137 kB]
Get:9 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libmagic1 amd64 1:5.25-2ubuntu1.1 [216 kB]
Get:10 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 file amd64 1:5.25-2ubuntu1.1 [21.2 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 4145 kB in 8s (517 kB/s)
Selecting previously unselected package libpython2.7-minimal:amd64.
(Reading database ... 14046 files and directories currently installed.)
Preparing to unpack .../libpython2.7-minimal_2.7.12-1ubuntu0~16.04.3_amd64.deb ...
Unpacking libpython2.7-minimal:amd64 (2.7.12-1ubuntu0~16.04.3) ...
Selecting previously unselected package python2.7-minimal.
Preparing to unpack .../python2.7-minimal_2.7.12-1ubuntu0~16.04.3_amd64.deb ...
Unpacking python2.7-minimal (2.7.12-1ubuntu0~16.04.3) ...
Selecting previously unselected package python-minimal.
Preparing to unpack .../python-minimal_2.7.12-1~16.04_amd64.deb ...
Unpacking python-minimal (2.7.12-1~16.04) ...
Selecting previously unselected package mime-support.
Preparing to unpack .../mime-support_3.59ubuntu1_all.deb ...
Unpacking mime-support (3.59ubuntu1) ...
Selecting previously unselected package libpython2.7-stdlib:amd64.
Preparing to unpack .../libpython2.7-stdlib_2.7.12-1ubuntu0~16.04.3_amd64.deb ...
Unpacking libpython2.7-stdlib:amd64 (2.7.12-1ubuntu0~16.04.3) ...
Selecting previously unselected package python2.7.
Preparing to unpack .../python2.7_2.7.12-1ubuntu0~16.04.3_amd64.deb ...
Unpacking python2.7 (2.7.12-1ubuntu0~16.04.3) ...
Selecting previously unselected package libpython-stdlib:amd64.
Preparing to unpack .../libpython-stdlib_2.7.12-1~16.04_amd64.deb ...
Unpacking libpython-stdlib:amd64 (2.7.12-1~16.04) ...
Setting up libpython2.7-minimal:amd64 (2.7.12-1ubuntu0~16.04.3) ...
Setting up python2.7-minimal (2.7.12-1ubuntu0~16.04.3) ...
Linking and byte-compiling packages for runtime python2.7...
Setting up python-minimal (2.7.12-1~16.04) ...
Selecting previously unselected package python.
(Reading database ... 14818 files and directories currently installed.)
Preparing to unpack .../python_2.7.12-1~16.04_amd64.deb ...
Unpacking python (2.7.12-1~16.04) ...
Selecting previously unselected package libmagic1:amd64.
Preparing to unpack .../libmagic1_1%3a5.25-2ubuntu1.1_amd64.deb ...
Unpacking libmagic1:amd64 (1:5.25-2ubuntu1.1) ...
Selecting previously unselected package file.
Preparing to unpack .../file_1%3a5.25-2ubuntu1.1_amd64.deb ...
Unpacking file (1:5.25-2ubuntu1.1) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Setting up mime-support (3.59ubuntu1) ...
Setting up libpython2.7-stdlib:amd64 (2.7.12-1ubuntu0~16.04.3) ...
Setting up python2.7 (2.7.12-1ubuntu0~16.04.3) ...
Setting up libpython-stdlib:amd64 (2.7.12-1~16.04) ...
Setting up python (2.7.12-1~16.04) ...
Setting up libmagic1:amd64 (1:5.25-2ubuntu1.1) ...
Setting up file (1:5.25-2ubuntu1.1) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Removing intermediate container fc2aeb8c23dd
 ---> 057807ccc7d8
Successfully built 057807ccc7d8
Successfully tagged hanshanyang/coj_demo_01:latest

docker build

安装完成我们

等他安装完成会把这个状态创建成一个image存在本地

然后我们在 push到docker hub上去（远程）和我们的git很相似

我们登录到docker hub上去（自己去官网创建账号）

登录上了

我们就要push了

这说明上传成功

那么从docker hub 下拉image也很简单就是 pull

如果你本地有这个image他会自动更新到最新的

如果你要删除

ASP.NET Core使用Docker-Swarm集群部署实现负载均衡实战演练

一、需求背景

人生苦短，我用.NET Core！阿笨对Docker是这样评价的：Docker在手，环境我有！Docker出手，集群我有！前面的Doc基础课程我们学习了如何使用Docker来部署搭建单机容器应用。当一台服务器的处理能力、存储空间不足时，不要企图去换更强大的服务器，对大型网站而言，不管多么强大的服务器，都满足不了网站持续增长的业务需求。实践中会发现，生产环境中使用单个 Docker 节点是远远不够的，搭建 Docker 集群势在必行。然而，面对 Kubernetes, Mesos等众多容器集群系统，我们该如何选择呢？它们之中，Docker Swarm 是 Docker 原生的，同时也是最简单，最易学，最节省资源的，比较适合中小型公司使用。今天给大家分享一下如何使用Docker-Swarm来搭建负载均衡集群容器环境应用。
1.1、本次分享课程适合人群如下：
1）、本课程一定需要具备Docker基础知识。(零基础学者止步慎入!)
2）、学习和了解ASP.Net Core跨平台开发技术。
3）、喜欢阿笨分享的干货课程童鞋们。本课程不是零基础教学，侧重点主要是讲解Docker Swarm与ASP.NET Core实战运用，大家务必根据自身的实际情况进行选择学习。
如果您在学习过程中遇到任何的课程问题，请先私下直接找阿笨老师进行在线的沟通和交流。谢谢大家的理解和支持，预祝大家学习快乐！
如果您是一个开发老鸟，那么本次课程完全不建议您进行学习！
1.2、一句话总结今天我们学习达到的目标
如何使用Docker-Swarm部署高可用ASP.NET Core负载均衡集群容器环境应用。
如果您同样对本次分享《ASP.NET Core使用Docker-Swarm集群部署实现负载均衡实战演练》课程感兴趣的话，那么请跟着阿笨一起学习吧。废话不多说，直接上干货，我们不生产干货，我们只是干货的搬运工。

1240

ASP.NET Core使用Docker-Swarm集群部署实现负载均衡实战演练

1240

ASP.NET Core使用Docker-Swarm集群部署实现负载均衡实战演练

二、Docker-Swarm概念介绍

1、什么是Docker Swarm

2、Docker Swarm核心概念解释

3、DockerSwarm特点

三、Docker-Swarm环境安装

可以通过Docker官方提供的docker-machine来快速创建一个docker容器环境的，它搭建和管理多个docker 主机同时搭建swarm集群。本期分享课程阿笨这里采用是直接模拟通过创建虚拟主机的方式来搭建我们的Docker Swarm集群环境。
Swarm是Docker原生的集群管理软件，与Kubernetes比起来比较简单。
对于没有集群使用经验的小白，用Docker Swarm起步，是一个很好的选择。Docker 可以看做集装箱把杂乱的货物一个个整理归类， Compose 则是用于编排这些集装箱，最后 Swarm 就是多提供几条船，挂掉一两条还能继续走，提高稳定性。

四、Docker-Swarm搭建ASP.NET Core集群应用环境

1240

ASP.NET Core使用Docker-Swarm集群部署实现负载均衡实战演练

五、Docker-Swarm集群部署Nginx实现ASP.NET Core应用负载均衡

1240

ASP.NET Core使用Docker-Swarm集群部署实现负载均衡实战演练

六、思考与总结

【网易云课堂】：点击在线观看

【腾讯课堂】：点击在线观看

【微信公众号】：跟着阿笨一起玩NET

我们今天的关于Docker 深入浅出系列 | Image 实战演练和docker image inspect的分享已经告一段落，感谢您的关注，如果您想了解更多关于#Docker# 深入浅出、(奇淫技巧)Docker的深入浅出、25.week4 docker build 也就是创建自己的image 上传image到dockerhub 从dockerhub下载images、ASP.NET Core使用Docker-Swarm集群部署实现负载均衡实战演练的相关信息，请在本站查询。

本文标签：