Docker检查的Config和ContainerConfig有什么不同？

Question

我docker inspect用来获取图像信息.我发现有Config和ContainerConfig输出,以及最大的价值是相同的,除了CMD.

在实践中,Config生效.因为我必须在运行命令中添加cmd. $ docker run -it debian bash

我想知道这两个项目的区别是什么？

$ docker inspect debian
[
{
    "Id": "7abab0fd74f97b6b398a1aca68735c5be153d49922952f67e8696a2225e1d8e1",
    ......
    "ContainerConfig": {
        "Hostname": "e5c68db50333",
        "Domainname": "",
        "User": "",
        "AttachStdin": false,
        "AttachStdout": false,
        "AttachStderr": false,
        "Tty": false,
        "OpenStdin": false,
        "StdinOnce": false,
        "Env": null,
        "Cmd": [
            "/bin/sh",
            "-c",
            "#(nop) CMD [\"/bin/bash\"]"
        ],
        "Image": "d8bd0657b25f17eef81a3d52b53da5bda4de0cf5cca3dcafec277634ae4b38fb",
        "Volumes": null,
        "WorkingDir": "",
        "Entrypoint": null,
        "OnBuild": null,
        "Labels": {}
    },
    "Config": {
        "Hostname": "e5c68db50333",
        "Domainname": "",
        "User": "",
        "AttachStdin": false,
        "AttachStdout": false,
        "AttachStderr": false,
        "Tty": false,
        "OpenStdin": false,
        "StdinOnce": false,
        "Env": null,
        "Cmd": [
            "/bin/bash"
        ],
        "Image": "d8bd0657b25f17eef81a3d52b53da5bda4de0cf5cca3dcafec277634ae4b38fb",
        "Volumes": null,
        "WorkingDir": "",
        "Entrypoint": null,
        "OnBuild": null,
        "Labels": {}
    },
    ......
}
]

Answer 1

如18880号所述,关于ContainerConfig:

您所看到的与图像创建历史有关.
尝试docker history ...在您的图片上运行,您将看到完整的历史记录.
Docker会将Dockerfile命令放入该CMD部分,以便跟踪该层/容器的创建方式.
它实际上只用于缓存查找目的(内部docker处理),并不打算由用户使用.

它也可见image/image.go:

// ContainerConfig is the configuration of the container that is committed into the image
ContainerConfig container.Config `json:"container_config,omitempty"`

例如,问题17780说明了一个空ContainerConfig:

图像的ContainerConfig是生成图像的容器.
对于您的图像,它不是从容器生成的,而是从运行生成的docker import.