An image is like a class and container is like an object that class and so you can have an infinite number of containers behaving like the image. A class is a blueprint which isnt doing anything on its own. You have to create instances of the object un your program to do anything meaningful. And so is the case with an image and a container. You define your image and then create containers running that image. It isnt exactly similar because object is an instance of a class whereas a container is something like an empty hollow place and you use the image to build up a running host with exactly what the image says

Dockerfile→(Build)→Image→(Run)→Container。

Dockerfile:包含一组Docker指令，以您喜欢的方式配置您的操作系统，并安装/配置所有软件。 图片:编译好的Dockerfile。节省了每次需要运行容器时重新构建Dockerfile的时间。这是一种隐藏供应代码的方法。 容器:虚拟操作系统本身。您可以ssh进入其中并运行任何命令，就像它是一个真实的环境一样。您可以从同一个映像运行1000多个容器。

在编程方面，

图片是源代码。

当编译和构建源代码时，它被称为应用程序。

类似于“当为映像创建实例时”，它被称为“容器”。

I would like to fill the missing part here between docker images and containers. Docker uses a union file system (UFS) for containers, which allows multiple filesystems to be mounted in a hierarchy and to appear as a single filesystem. The filesystem from the image has been mounted as a read-only layer, and any changes to the running container are made to a read-write layer mounted on top of this. Because of this, Docker only has to look at the topmost read-write layer to find the changes made to the running system.

An image is like a class and container is like an object that class and so you can have an infinite number of containers behaving like the image. A class is a blueprint which isnt doing anything on its own. You have to create instances of the object un your program to do anything meaningful. And so is the case with an image and a container. You define your image and then create containers running that image. It isnt exactly similar because object is an instance of a class whereas a container is something like an empty hollow place and you use the image to build up a running host with exactly what the image says

我认为最好一开始就解释清楚。

假设你运行命令docker run hello-world。会发生什么呢?

它调用Docker CLI，负责接收Docker命令并转换为调用Docker服务器命令。一旦Docker服务器得到一个运行映像的命令，它就会检查映像缓存中是否有这样一个名称的映像。

假设hello-world不存在。Docker服务器访问Docker Hub (Docker Hub只是一个免费的图像存储库)并询问，嘿，Hub，你有一个名为hello-world的图像吗? 枢纽响应-是的，我有。那就请给我吧。下载过程开始了。一旦Docker镜像下载完成，Docker服务器就会将其放入镜像缓存中。

所以在我们解释Docker镜像和Docker容器是什么之前，让我们先来介绍一下你电脑上的操作系统以及它是如何运行软件的。

例如，当你在电脑上运行Chrome时，它会调用操作系统，操作系统自己会调用内核并请求，嘿，我想运行这个程序。内核设法从您的硬盘运行文件。

现在假设你有两个程序，Chrome和Node.js。Chrome需要Python版本2才能运行，Node.js需要Python版本3才能运行。如果您的计算机上只安装了Python v2，则只能运行Chrome。

为了使这两种情况都能工作，您需要以某种方式使用称为名称空间的操作系统特性。命名空间是一种特性，它使您有机会隔离进程、硬盘驱动器、网络、用户、主机名等。

当我们讨论映像时，我们实际上是在讨论文件系统快照。映像是一个物理文件，其中包含构建特定容器的方向和元数据。容器本身是一个映像的实例;它使用名称空间隔离硬盘驱动器，该名称空间仅对该容器可用。因此容器是一个进程或一组进程，它将分配给它的不同资源分组。