blocks|key|921662|text|docker+history+<image>|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|921663|差不多就是这样。|unstyled|921664|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>docker history &lt;image&gt;
</code></pre>

Does pretty much that.

blocks|key|2969267|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2969268|是否有可能恢复为生成给定的docker映像而运行的docker命令？|blockquote|2969269|2969270|2969271|不，考虑到你有像docker+export+/+docker+import这样的命令，它允许平面化图像：|offset|length|style|CODE|2969272|docker+export+<containerID>+%7C+docker+import+-+<imagename>|code-block|syntax|javascript|2969273|生成的图像将从一个容器构建，并且只包含一个层。即使是docker+history也无法提供关于原始图像及其Dockerfile文件的线索，这些Dockerfile文件是原始容器的一部分。|2969274|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.docker.com/engine/reference/commandline/export/|1|https://docs.docker.com/engine/reference/commandline/import/^0|0|0|0|0|8|D|O|D|8|D|0|O|D|1|0|0|Q|E|0^^$0|@$1|2|3|-4|4|5|6|12|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|13|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|14|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|15|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|16|7|@$H|17|I|18|J|K]|$H|19|I|1A|J|K]]|8|@$H|1B|I|1C|1|1D]|$H|1E|I|1F|1|1G]]|9|$]]|$1|L|3|M|4|N|6|1H|7|@]|8|@]|9|$O|P]]|$1|Q|3|R|4|5|6|1I|7|@$H|1J|I|1K|J|K]]|8|@]|9|$]]|$1|S|3|-4|4|5|6|1L|7|@]|8|@]|9|$]]]|T|$U|$4|V|W|X|9|$Y|Z]]|10|$4|V|W|X|9|$Y|11]]]]

<blockquote>
 Is it possible to get back the docker commands which were run to produce a given docker image? 
</blockquote>

No, considering you have commands like <a href="https://docs.docker.com/engine/reference/commandline/export/" rel="nofollow"><code>docker export</code></a> / <a href="https://docs.docker.com/engine/reference/commandline/import/" rel="nofollow"><code>docker import</code></a> which allows to flatten an image:

<pre><code>docker export &lt;containerID&gt; | docker import - &lt;imagename&gt;
</code></pre>

The resulting image would be build from a container, and include only one layer. Not even a <code>docker history</code> would be able to give clues as to the original images and their Dockerfile which where part of the original container.

blocks|key|921687|text|您可以使用两个docker命令的组合来实现您想要的效果：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|921688|docker+inspect+<image>|code-block|syntax|javascript|921689|和|921690|docker+history+<image>|921691|或者你可以使用这个很酷的服务来查看图像是如何生成的，每一层都是你docker文件中的一个命令：|921692|https://imagelayers.io/?images=java:latest,golang:latest,node:latest,python:latest,php:latest,ruby:latest|offset|length|921693|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|0|0|2X|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Y|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Z|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|10|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|11|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|12|8|@]|9|@$O|13|P|14|1|15]]|A|$]]|$1|Q|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|N]]]]

You can use combinations of two docker commands to achieve what you want:

<pre><code>docker inspect &lt;image&gt;
</code></pre>

and 

<pre><code>docker history &lt;image&gt;
</code></pre>

Or you can use this cool service to see how that image being generated, each layer is a command in your docker file:

<a href="https://imagelayers.io/?images=java:latest,golang:latest,node:latest,python:latest,php:latest,ruby:latest" rel="nofollow">https://imagelayers.io/?images=java:latest,golang:latest,node:latest,python:latest,php:latest,ruby:latest</a>

blocks|key|2969224|text|我想这取决于你从哪里得到的图像。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2969225|在these+docker+containers+of+mine+from+the+Docker+Hub的情况下，您可以使用this+link+from+the+right+hand+side+of+the+webpage将其跟踪到this+github+repo+containing+the+Dockerfile(s)。|offset|length|2969226|我不认为有一个命令可以“反汇编”一个容器/镜像，然后找回生成它的指令。|2969227|entityMap|0|LINK|mutability|MUTABLE|url|https://registry.hub.docker.com/u/eddelbuettel/docker-debian-r/|1|https://github.com/eddelbuettel/docker-debian-r.git|2|https://github.com/eddelbuettel/docker-debian-r^0|0|1|1F|0|1Q|1D|1|38|19|2|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@$D|V|E|W|1|X]|$D|Y|E|Z|1|10]|$D|11|E|12|1|13]]|A|$]]|$1|F|3|G|5|6|7|14|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]|R|$5|K|L|M|A|$N|S]]]]

I guess it depends on where you got the image from. 

In the case of <a href="https://registry.hub.docker.com/u/eddelbuettel/docker-debian-r/" rel="nofollow">these docker containers of mine from the Docker Hub</a> you can use 
<a href="https://github.com/eddelbuettel/docker-debian-r.git" rel="nofollow">this link from the right hand side of the webpage</a> to follow it to <a href="https://github.com/eddelbuettel/docker-debian-r" rel="nofollow">this github repo containing the Dockerfile(s)</a>.

I do not think there is a command to "unassemble" a container / image and get back the instructions which made it.

blocks|key|654629|text|对于您创建的图像，可以使用图像元数据(标签)来存储Dockerfile+https://docs.docker.com/engine/userguide/labels-custom-metadata/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|654630|这里提出了最初的解决方案https://speakerdeck.com/garethr/managing-container-configuration-with-metadata|654631|这种存储Dockerfile的方法效率不高-它需要启动容器才能解压Dockerfile。|654632|我个人使用不同的方法-用Base64编码Dockerfile，并使用外部参数传递这样的编码字符串来设置图像标签。这样您就可以使用inspect直接从镜像中读取Dockerfile的内容。你可以在这里找到详细的例子：https://gist.github.com/lruslan/3dea3b3d52a66531b2a1|654633|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.docker.com/engine/userguide/labels-custom-metadata/|1|https://speakerdeck.com/garethr/managing-container-configuration-with-metadata|2|https://gist.github.com/lruslan/3dea3b3d52a66531b2a1^0|10|1S|0|0|C|26|1|0|0|2Z|1G|2|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|D|3|E|5|6|7|Z|8|@]|9|@$A|10|B|11|1|12]]|C|$]]|$1|F|3|G|5|6|7|13|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|14|8|@]|9|@$A|15|B|16|1|17]]|C|$]]|$1|J|3|-4|5|6|7|18|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]|R|$5|M|N|O|C|$P|S]]|T|$5|M|N|O|C|$P|U]]]]

For the images you create image metadata (labels) can be used to store Dockerfile
 <a href="https://docs.docker.com/engine/userguide/labels-custom-metadata/" rel="nofollow">https://docs.docker.com/engine/userguide/labels-custom-metadata/</a>

Initial solution was proposed here <a href="https://speakerdeck.com/garethr/managing-container-configuration-with-metadata" rel="nofollow">https://speakerdeck.com/garethr/managing-container-configuration-with-metadata</a>

This approach of storing Dockerfile is not very efficient - it requires container to be started in order to extract the Dockerfile.

I personally use different approach - encode Dockerfile with Base64 and pass such encoded string using external arguments to set image label. This way you can read content of Dockerfile directly from image using inspect. 
You can find detailed example here: <a href="https://gist.github.com/lruslan/3dea3b3d52a66531b2a1" rel="nofollow">https://gist.github.com/lruslan/3dea3b3d52a66531b2a1</a>

Is it possible to get back the docker commands which were run to produce a given docker image? Since each line of a docker file should map to a single layer, it seems this would be possible, but I don't see anything in the docs.

Get dockerfile / docker commands from docker image

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

是否有可能恢复为生成给定的docker图像而运行的docker命令？由于docker文件的每一行都应该映射到一个层，这似乎是可能的，但我在文档中看不到任何东西。

问从docker镜像获取dockerfile / docker命令
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问从docker镜像获取dockerfile / docker命令EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问从docker镜像获取dockerfile / docker命令
EN