Shulou(Shulou.com)06/01 Report--

This article mainly shows you the "sample Analysis of Docker Image", which is easy to understand and well-organized. I hope it can help you solve your doubts. Let the editor lead you to study and learn the article "sample Analysis of Docker Image".

One: mind mapping

Second: the life cycle of the mirror image

Third, the organizational structure of the mirror image.

4: mirrored data structure

Docker inspect busybox:latest

[{"Id": "sha256:8c811b4aec35f259572d0f79207bc0678df4c736eeec50bc9fec37ed936a472a", "RepoTags": ["docker.io/busybox:latest"], "RepoDigests": ["docker.io/busybox@sha256:141c253bc4c3fd0a201d32dc1f493bcf3fff003b6df416dea4f41046e0f37d47"], "Parent": "," Comment ":"," Created ":" 2018-05-23T21:19:31.132152818Z " "Container": "617bfbb850a66642161d4925e0c00f77caa46e22057409788207e7b2edb86c3e", "ContainerConfig": {"Hostname": "617bfbb850a6", "Domainname": "," User ":"," AttachStdin ": false," AttachStdout ": false," AttachStderr ": false," Tty ": false," OpenStdin ": false "StdinOnce": false, "Env": ["PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"], "Cmd": ["/ bin/sh", "- c", "# (nop)" "CMD [\" sh\ "]]," ArgsEscaped ": true," Image ":" sha256:3e8a1c5213eb57c6ea8ddb27d86a241698741ce60d9053b641f57a7e455f6842 "," Volumes ": null," WorkingDir ":"," Entrypoint ": null," OnBuild ": null," Labels ": {}} "DockerVersion": "17.06.2-ce", "Author": "", "Config": {"Hostname": "," Domainname ":", "User": "", "AttachStdin": false, "AttachStdout": false, "AttachStderr": false, "Tty": false "OpenStdin": false, "StdinOnce": false, "Env": ["PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"], "Cmd": ["sh"], "ArgsEscaped": true "Image": "sha256:3e8a1c5213eb57c6ea8ddb27d86a241698741ce60d9053b641f57a7e455f6842", "Volumes": null, "WorkingDir": "," Entrypoint ": null," OnBuild ": null," Labels ": null}," Architecture ":" amd64 "," Os ":" linux "," Size ": 1146369," VirtualSize ": 1146369 "GraphDriver": {"Name": "overlay", "Data": {"RootDir": "/ var/lib/docker/overlay/4f7e0d9cff96526ac13d288d22e27be31f9fc8c7e5976aa3640a4ac2d0b2c7fb/root"}}, "RootFS": {"Type": "layers" "Layers": ["sha256:432b65032b9466b4dadcc5c7b11701e71d21c18400aae946b101ad16be62333a"]}}]

A.Id: Image's ID is actually just the top layerID.

B.Parent: the parent layer of the layer, which can recursively get all the layer information of an Image

C.Comment: very similar to Git's commit message

D.Container: container startup needs to use image as a template, but you can save the container as an image, so generally speaking, each layer of image is saved in a container, so the container can be said to be a "template" of image layer.

E.Config contains some configuration information for the image

F.Architecture: the CPU architecture corresponding to the image. Now Docker officially supports amd64.

The above is all the contents of the article "sample Analysis of Docker Images". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.