映像:运行容器所需的文件系统和元数据。它们可以被认为是一种应用程序打包格式，其中包括运行应用程序的所有依赖项，以及执行该应用程序的默认设置。元数据包括要运行的命令的默认值、环境变量、标签和healthcheck命令。

容器:孤立应用程序的实例。容器需要映像来定义其初始状态，并使用映像中的只读文件系统以及容器特定的读写文件系统。正在运行的容器是正在运行的进程的包装器，为文件系统、网络和pid等提供进程名称空间。

当您执行docker run命令时，您在命令行上提供一个映像以及任何配置，docker根据您提供的映像定义和配置返回一个容器。

References: to the docker engine, an image is just an image id. This is a unique immutable hash. A change to an image results in creating a new image id. However, you can have one or more references pointing to an image id, not unlike symbolic links. And these references can be updated to point to new image id's. Note that when you create a container, docker will resolve that reference at the time of container creation, so you cannot update the image of a running container. Instead, you create a new image, and create a new container based on that new image.

Layers: Digging a bit deeper, you have filesystem layers. Docker assembles images with a layered filesystem. Each layer is a read-only set of changes to the filesystem, and that layer is represented by a unique hash. Using these read-only layers, multiple images may extend another, and only the differences between those images need to be stored or transmitted over the network. When a Docker container is run, it receives a container specific read-write filesystem layer unique to that container, and all of the image layers are assembled with that using a union filesystem. A read is processed through each layer until the file is found, a deletion is found, or the file is not found in the bottom layer. A write performs a copy-on-write from the image read-only layer to the container specific read-write layer. And a deletion is recorded as a change to the container specific read-write layer. A common step in building images is to run a command in a temporary container based off the previous image filesystem state and save the resulting container specific layer as a layer in the new image.

码头工人图片: 它包含一个关于如何构建和运行容器的命令和指令列表。因此，基本上Images包含启动容器(也称为blueprint)所需的所有数据和元数据。我们不能在没有指定图像的情况下将一个容器送入午餐。

$docker images centos

列出所有可用的centos版本。

码头工人容器: 容器是图像的午餐，因此我们可以说容器是图像的运行实例。 Container是一个运行时构造，不像Images是构建时构造。

图片是用你的手机拍的照片。 容器就是电话。

DockerFile——(构建)——> DockerImage——(运行)——> DockerContainer

DockerFile是你或开发人员编写代码来做某事的文件(安装前)

Docker Image是你在构建Docker文件时得到的。

Docker容器是你运行Docker镜像时得到的

我们可以通过拖动Docker hub来获取Docker Image，然后运行它来获取container。

使用面向对象编程的类比，Docker镜像和Docker容器之间的区别就像类和对象之间的区别一样。对象是类的运行时实例。类似地，容器是映像的运行时实例。

对象在实例化时只创建一次。类似地，容器可以运行也可以停止。容器是根据映像创建的，尽管情况可能并不总是如此。下面的例子创建一个Apache服务器镜像，运行镜像，列出镜像，然后列出容器:

创建一个Dockerfile，内容如下: 从httpd: 2.4 安装Apache服务器 Sudo docker build -t my-apache2。 运行映像 Sudo docker运行-it——rm——命名my-running-app my-apache2 列出Docker映像 Sudo docker图像 列出正在运行的Docker容器 码头工人ps 列出所有容器 Docker ps a 列出最新创建的容器 Docker ps -l

映像基本上是用于创建容器的不可变模板。通过考虑将图像转换为容器所发生的变化，可以更容易地理解图像和容器之间的区别。

The Docker engine takes the image and adds a read-write filesystem on top, then initialises various settings. These settings include network options (IP, port, etc.), name, ID, and any resource limits (CPU, memory). If the Docker engine has been asked to run the container it will also initialise a process inside it. A container can be stopped and restarted, in which case it will retain all settings and filesystem changes (but will lose anything in memory and all processes will be restarted). For this reason a stopped or exited container is not the same as an image.