blocks|key|2372929|text|在某些情况下(如我的例子)，您可能试图通过指定图像id来删除图像，该图像id有多个标记()，您没有意识到这些标记是存在的，其中一些标记可能被其他图像所使用。在这种情况下，您可能不想删除图像。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2372930|如果您有这里描述的冗余标记的情况，那么在您希望删除的冗余标记上使用docker+rmi+<image_id>而不是docker+rmi+<repo:tag>。|CODE|2372931|entityMap^0|W|C|2D|9|0|X|L|1L|L|0^^$0|@$1|2|3|4|5|6|7|K|8|@$9|L|A|M|B|C]|$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|P|8|@$9|Q|A|R|B|H]|$9|S|A|T|B|H]]|D|@]|E|$]]|$1|I|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|J|$]]

In some cases (like in my case) you may be trying to delete an image by specifying the image id that has multiple tags that you don't realize exist, some of which may be used by other images. In which case, you may not want to remove the image.

If you have a case of redundant tags as described here, instead of <code>docker rmi &lt;image_id&gt;</code> use <code>docker rmi &lt;repo:tag&gt;</code> on the redundant tag you wish to remove.

blocks|key|2372524|text|在删除图像之前，您应该尝试删除不必要的图像：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2372525|docker+rmi+$(docker+images+--filter+"dangling=true"+-q+--no-trunc)|code-block|syntax|javascript|2372526|在那之后，跑：|2372527|docker+rmi+c565603bc87f|2372528|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

You should try to remove unnecessary images before removing the image:

<pre><code>docker rmi $(docker images --filter "dangling=true" -q --no-trunc)
</code></pre>

After that, run:

<pre><code>docker rmi c565603bc87f
</code></pre>

blocks|key|1620005|text|前面的所有答案都是正确的，但是这里有一个解决方案，就是强制删除所有的图像(使用这个命令将承担您自己的风险，它将删除所有的图像)|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1620006|docker+rmi+$(docker+images+-q)+-f|code-block|syntax|javascript|1620007|​|1620008|📷|atomic|1620009|1620010|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/bd4e5d35ec01024a8e725aaa54aef1ec.png|imageAlt^0|11|P|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|12|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|13|8|@]|D|@]|E|$]]|$1|M|3|N|5|O|7|14|8|@]|D|@$9|15|A|16|1|17]]|E|$]]|$1|P|3|L|5|6|7|18|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|19|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X|Y|-4]]]]

all previous answers are correct but here is one solution which is just deleteing all of your images forcefully (use this command at your own risk it will delete all of your images)

<pre><code>docker rmi $(docker images -q) -f
</code></pre>

<a href="https://i.stack.imgur.com/fcXTw.png" rel="noreferrer"><img src="https://i.stack.imgur.com/fcXTw.png" alt="enter image description here"></a>

blocks|key|1619802|text|使用以下内容查找在所涉图像之后创建的所有图像的图像id和父id：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1619803|docker+inspect+--format='{{.Id}}+{{.Parent}}'+$(docker+images+--filter+since=<image_id>+-q)|code-block|syntax|javascript|1619804|然后调用命令：|1619805|docker+rmi+{sub_image_id}+|1619806|"sub_image_id“是相依图像的ID。|1619807|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

find the image id and parent id for all image created after the image in question with the following: 

<pre><code>docker inspect --format='{{.Id}} {{.Parent}}' $(docker images --filter since=&lt;image_id&gt; -q)
</code></pre>

Then you call command:

<pre><code>docker rmi {sub_image_id} 
</code></pre>

"sub_image_id" is ID of dependent image

blocks|key|2373125|text|对我来说起作用的是使用存储库:标记组合，而不是图像ID。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2373126|当我尝试使用命令docker+rmi+<IMAGE+ID>删除一个没有与此映像关联的容器的停靠者映像时，我收到了以下消息：|offset|length|style|CODE|2373127|$+docker+rmi+3f66bec2c6bf
Error+response+from+daemon:+conflict:+unable+to+delete+3f66bec2c6bf+(cannot+be+forced)+-+image+has+dependent+child+images|code-block|syntax|javascript|2373128|当我使用命令docker+rmi+RPOSITORY:TAG时，我可以成功地删除|2373129|$+docker+rmi+ubuntu:18.04v1
Untagged:+ubuntu:18.04v1|2373130|entityMap^0|0|8|L|0|0|6|O|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@$D|U|E|V|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|W|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|X|8|@$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|O|3|P|5|J|7|10|8|@]|9|@]|A|$K|L]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

What worked to me was to use the REPOSITORY:TAG combination rather than IMAGE ID.

When I tried to delete a docker image with the command <code>docker rmi &lt;IMAGE ID&gt;</code> with no containers associated with this image I had the message:

<pre><code>$ docker rmi 3f66bec2c6bf
Error response from daemon: conflict: unable to delete 3f66bec2c6bf (cannot be forced) - image has dependent child images
</code></pre>

I could delete with success when I used the command <code>docker rmi RPOSITORY:TAG</code> 

<pre><code>$ docker rmi ubuntu:18.04v1
Untagged: ubuntu:18.04v1
</code></pre>

blocks|key|2373094|text|此命令删除所有图像(小心使用)|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2373095|你试过用武力吗？|2373096|sudo+docker+rmi+$(sudo+docker+images+-aq)+--force|code-block|syntax|javascript|2373097|上面的代码运行起来很有魅力，甚至我也有过同样的问题。|2373098|entityMap^0|0|F|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|U|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|V|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|P|$]]

THIS COMMAND REMOVES ALL IMAGES (USE WITH CAUTION)

Have you tried to use --force

<pre><code>sudo docker rmi $(sudo docker images -aq) --force
</code></pre>

This above code run like a charm even doe i had the same issue

blocks|key|2373290|text|如果你想Untag+Docker+Images|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2373291|docker+rmi+<rep:tag>|code-block|syntax|javascript|2373292|如果你想Removing+Docker+Images|2373293|docker+image+rm+<image_id>|2373294|例:输入docker+image+ls显示图像信息|2373295|REPOSITORY++++++++++TAG+++++++++++++++++IMAGE+ID++++++++++++CREATED+++++++++++++SIZE
python++++++++++++++3.6++++++++++++60f85556d5d2++++++++4+days+ago++++++++++174MB|2373296|docker+rmi+python:3.6码头图像rm+60f85556d5d2|blockquote|2373297|entityMap^0|4|J|0|0|4|M|0|0|4|F|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|10|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|11|8|@$9|12|A|13|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|14|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|15|8|@$9|16|A|17|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|H|7|18|8|@]|D|@]|E|$I|J]]|$1|S|3|T|5|U|7|19|8|@]|D|@]|E|$]]|$1|V|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|W|$]]

If you want to <code>Untag Docker Images</code>
<pre><code>docker rmi &lt;rep:tag&gt;
</code></pre>
If you want to <code>Removing Docker Images</code>
<pre><code>docker image rm &lt;image_id&gt;
</code></pre>
Ex: Type <code>docker image ls</code> to show info of Images
<pre><code>REPOSITORY TAG IMAGE ID CREATED SIZE
python 3.6 60f85556d5d2 4 days ago 174MB
</code></pre>
<blockquote>
docker rmi python:3.6
</blockquote>
<blockquote>
docker image rm 60f85556d5d2
</blockquote>

blocks|key|1619849|text|这里有一个脚本来删除一个图像和所有依赖它的图像。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1619850|#!/bin/bash

if+[[+$#+-lt+1+]];+then
++++echo+must+supply+image+to+remove;
++++exit+1;
fi;

get_image_children+()
{
++++ret=()
++++for+i+in+$(docker+image+ls+-a+--no-trunc+-q);+do
++++++++#>&2+echo+processing+image+"$i";
++++++++#>&2+echo+parent+is+$(docker+image+inspect+--format+'{{.Parent}}'+"$i")
++++++++if+[[+"$(docker+image+inspect+--format+'{{.Parent}}'+"$i")"+==+"$1"+]];+then
++++++++++++ret%2B=("$i");
++++++++fi;
++++done;
++++echo+"${ret[@]}";
}

realid=$(docker+image+inspect+--format+'{{.Id}}'+"$1")
if+[[+-z+"$realid"+]];+then
++++echo+"$1+is+not+a+valid+image.";
++++exit+2;
fi;
images_to_remove=("$realid");
images_to_process=("$realid");
while+[[+"${#images_to_process[@]}"+-gt+0+]];+do
++++children_to_process=();
++++for+i+in+"${!images_to_process[@]}";+do
++++++++children=$(get_image_children+"${images_to_process[$i]}");
++++++++if+[[+!+-z+"$children"+]];+then
++++++++++++#+allow+word+splitting+on+the+children.
++++++++++++children_to_process%2B=($children);
++++++++fi;
++++done;
++++if+[[+"${#children_to_process[@]}"+-gt+0+]];+then
++++++++images_to_process=("${children_to_process[@]}");
++++++++images_to_remove%2B=("${children_to_process[@]}");
++++else
++++++++#no+images+have+any+children.+We're+done+creating+the+graph.
++++++++break;
++++fi;
done;
echo+images_to_remove+=+"$(printf+%25s\n+"${images_to_remove[@]}")";
indices=(${!images_to_remove[@]});
for+((i="${#indices[@]}"+-+1;+i+>=+0;+--i))+;+do
++++image_to_remove="${images_to_remove[indices[i]]}"
++++if+[[+"${image_to_remove:0:7}"+==+"sha256:"+]];+then
++++++++image_to_remove="${image_to_remove:7}";
++++fi
++++echo+removing+image+"$image_to_remove";
++++docker+rmi+"$image_to_remove";
done|code-block|syntax|javascript|1619851|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Here's a script to remove an image and all the images that depend on it.

<pre><code>#!/bin/bash

if [[ $# -lt 1 ]]; then
 echo must supply image to remove;
 exit 1;
fi;

get_image_children ()
{
 ret=()
 for i in $(docker image ls -a --no-trunc -q); do
 #&gt;&amp;2 echo processing image "$i";
 #&gt;&amp;2 echo parent is $(docker image inspect --format '{{.Parent}}' "$i")
 if [[ "$(docker image inspect --format '{{.Parent}}' "$i")" == "$1" ]]; then
 ret+=("$i");
 fi;
 done;
 echo "${ret[@]}";
}

realid=$(docker image inspect --format '{{.Id}}' "$1")
if [[ -z "$realid" ]]; then
 echo "$1 is not a valid image.";
 exit 2;
fi;
images_to_remove=("$realid");
images_to_process=("$realid");
while [[ "${#images_to_process[@]}" -gt 0 ]]; do
 children_to_process=();
 for i in "${!images_to_process[@]}"; do
 children=$(get_image_children "${images_to_process[$i]}");
 if [[ ! -z "$children" ]]; then
 # allow word splitting on the children.
 children_to_process+=($children);
 fi;
 done;
 if [[ "${#children_to_process[@]}" -gt 0 ]]; then
 images_to_process=("${children_to_process[@]}");
 images_to_remove+=("${children_to_process[@]}");
 else
 #no images have any children. We're done creating the graph.
 break;
 fi;
done;
echo images_to_remove = "$(printf %s\n "${images_to_remove[@]}")";
indices=(${!images_to_remove[@]});
for ((i="${#indices[@]}" - 1; i &gt;= 0; --i)) ; do
 image_to_remove="${images_to_remove[indices[i]]}"
 if [[ "${image_to_remove:0:7}" == "sha256:" ]]; then
 image_to_remove="${image_to_remove:7}";
 fi
 echo removing image "$image_to_remove";
 docker rmi "$image_to_remove";
done
</code></pre>

blocks|key|1211833|text|尝试删除图像id：b721d1cdaac7|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1211834|docker+rmi+b721d1cdaac7+-f|code-block|syntax|javascript|1211835|响应:来自守护进程的错误响应:冲突:无法删除b721d1cdaac7+(不能强制)-图像有依赖的子图像|1211836|要删除所有子图像命令，请执行以下操作：|1211837|++docker+image+rm+$(docker+images+--filter+since=b721d1cdaac7+-q)+-f|1211838|它将首先取消标记并删除所有的子图像。|1211839|entityMap^0|9|C|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|Z|8|@]|D|@]|E|$]]|$1|O|3|P|5|H|7|10|8|@]|D|@]|E|$I|J]]|$1|Q|3|R|5|6|7|11|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|T|$]]

Trying to delete image id : b721d1cdaac7
<pre><code>docker rmi b721d1cdaac7 -f
</code></pre>
Response : Error response from daemon: conflict: unable to delete b721d1cdaac7 (cannot be forced) - image has dependent child images
To delete all child images command :
<pre><code> docker image rm $(docker images --filter since=b721d1cdaac7 -q) -f
</code></pre>
It will first untagged and removed all child images

blocks|key|1211473|text|这里的答案是找到所有的后代子女，在这里有一个答案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1211474|道克，我怎样才能得到受抚养的孩子图像的列表？|offset|length|1211475|然后按顺序使用该方法删除子图像。|1211476|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/36584122/docker-how-can-i-get-the-list-of-dependent-child-images^0|0|0|M|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

The answer here is to find all descendent children, which has an answer here:

<a href="https://stackoverflow.com/questions/36584122/docker-how-can-i-get-the-list-of-dependent-child-images">docker how can I get the list of dependent child images?</a>

Then use that to remove the child images in order.

blocks|key|1214560|text|#+docker+rm+$(docker+ps+-aq)|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1214561|在此之后，使用Nguyen建议的命令。|unstyled|1214562|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 rm $(docker ps -aq)
</code></pre>

After that use the command as Nguyen suggested.

blocks|key|1620033|text|在Simon的蛮力方法这里的基础上，如果您没有大量的图像，可以使用这个shell函数：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1620034|recursive_remove_image()+{
++for+image+in+$(docker+images+--quiet+--filter+"since=${1}")
++do
++++if+[+$(docker+history+--quiet+${image}+%7C+grep+${1})+]
++++then
++++++recursive_remove_image+"${image}"
++++fi
++done
++echo+"Removing:+${1}"
++docker+rmi+-f+${1}
}|code-block|syntax|javascript|1620035|然后使用recursive_remove_image+<image-id>调用它。|style|CODE|1620036|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/41176677/3273031^0|B|2|0|0|0|4|X|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|Z|8|@$A|10|B|11|K|L]]|9|@]|C|$]]|$1|M|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

Building on Simon Brady's brute force method <a href="https://stackoverflow.com/a/41176677/3273031">here</a>, if you don't have a ton of images you can use this shell function:

<pre><code>recursive_remove_image() {
 for image in $(docker images --quiet --filter "since=${1}")
 do
 if [ $(docker history --quiet ${image} | grep ${1}) ]
 then
 recursive_remove_image "${image}"
 fi
 done
 echo "Removing: ${1}"
 docker rmi -f ${1}
}
</code></pre>

and then call it using <code>recursive_remove_image &lt;image-id&gt;</code>.

blocks|key|2373348|text|请运行这个停靠命令|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2373349|docker+image+rm+-f+$(docker+image+ls+--filter+dangling=true+-q)|ordered-list-item|offset|length|style|CODE|2373350|然后跑|2373351|docker+image+rm+-f+$(docker+image+ls+-a+-q)|2373352|在工作了许多小时之后，我发现上面的命令非常有用。|2373353|否则，您可以运行prune脚本。https://gist.github.com/sethbergman/cb0f1f700b1f6474b9738191055c9fb7|2373354|entityMap|0|LINK|mutability|MUTABLE|url|https://gist.github.com/sethbergman/cb0f1f700b1f6474b9738191055c9fb7^0|0|0|1R|0|0|0|17|0|0|G|1W|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@$E|10|F|11|G|H]]|9|@]|A|$]]|$1|I|3|J|5|6|7|12|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|13|8|@$E|14|F|15|G|H]]|9|@]|A|$]]|$1|M|3|N|5|6|7|16|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|17|8|@]|9|@$E|18|F|19|1|1A]]|A|$]]|$1|Q|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

Please run this docker command
<ol>
<li><code>docker image rm -f $(docker image ls --filter dangling=true -q)</code></li>
</ol>
and then run
<ol start="2">
<li><code>docker image rm -f $(docker image ls -a -q)</code></li>
</ol>
I found the above commands very helpful after working for many hours.
<ol start="3">
<li>Otherwise, you can run prune script.
<a href="https://gist.github.com/sethbergman/cb0f1f700b1f6474b9738191055c9fb7" rel="noreferrer">https://gist.github.com/sethbergman/cb0f1f700b1f6474b9738191055c9fb7</a></li>
</ol>

blocks|key|2373013|text|当我想删除一些名为"<none>"的未使用的图像时，我要面对解决这个问题的unable+to+delete+a354bbc7c9b7+(cannot+be+forced)+-+image+has+dependent+child+images.So问题：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2373014|数独码头ps+-a|blockquote|2373015|CONTAINER+ID++++++++IMAGE+++++++++++++++++++++++COMMAND++++++++++++++++++CREATED+++++++++++++STATUS+++++++++++++++++++++++++PORTS++++++++++++++++++++++++++++++++++++++++++++++NAMES
01ee1276bbe0++++++++lizard:1++++++++++++++++++++"/bin/sh+-c+'java+..."+++About+an+hour+ago+++Exited+(1)+About+an+hour+ago++++++++++++++++++++++++++++++++++++++++++++++++++++++objective_lewin
49d73d8fb023++++++++javaapp:latest++++++++++++++"/usr/bin/java+-ja..."+++19+hours+ago++++++++Up+19+hours++++++++++++++++++++0.0.0.0:8091->8091/tcp+++++++++++++++++++++++++++++pedantic_bell
405fd452c788++++++++javaapp:latest++++++++++++++"/usr/bin/java+-ja..."+++19+hours+ago++++++++Created+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++infallible_varahamihira
532257a8b705++++++++javaapp:latest++++++++++++++"/usr/bin/java+-ja..."+++19+hours+ago++++++++Created+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++demo-default
9807158b3fd5++++++++javaapp:latest++++++++++++++"/usr/bin/java+-ja..."+++19+hours+ago++++++++Created+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++xenodochial_kilby
474930241afa++++++++jenkins+++++++++++++++++++++"/bin/tini+--+/usr..."+++13+days+ago+++++++++Up+4+days++++++++++++++++++++++0.0.0.0:8080->8080/tcp,+0.0.0.0:50000->50000/tcp+++myjenkins
563d8c34682f++++++++mysql/mysql-server:latest+++"/entrypoint.sh+my..."+++3+weeks+ago+++++++++Up+4+days+(healthy)++++++++++++0.0.0.0:3306->3306/tcp,+33060/tcp++++++++++++++++++mymysql
b4ca73d45d20++++++++phpmyadmin/phpmyadmin+++++++"/run.sh+phpmyadmin"+++++4+weeks+ago+++++++++Exited+(0)+3+weeks+ago++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++phpmyadmin|code-block|syntax|javascript|2373016|您可以看到，我有几个名称为javaapp的图片:最新的和不同的容器名称。因此，我用:杀死并删除了“javaapp:最新”容器的所有容器：|2373017|数独码头停"containerName“
数独码头rm+"containrName“|2373018|然后|2373019|数独码头客rmi+-f+"imageId“|2373020|所以我可以删除所有名字"<none>"的图像|2373021|祝你好运|2373022|entityMap^0|9|8|11|2B|0|0|0|0|0|0|0|B|8|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@$9|12|A|13|B|C]|$9|14|A|15|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|16|8|@]|D|@]|E|$]]|$1|I|3|J|5|K|7|17|8|@]|D|@]|E|$L|M]]|$1|N|3|O|5|6|7|18|8|@]|D|@]|E|$]]|$1|P|3|Q|5|H|7|19|8|@]|D|@]|E|$]]|$1|R|3|S|5|6|7|1A|8|@]|D|@]|E|$]]|$1|T|3|U|5|H|7|1B|8|@]|D|@]|E|$]]|$1|V|3|W|5|6|7|1C|8|@$9|1D|A|1E|B|C]]|D|@]|E|$]]|$1|X|3|Y|5|6|7|1F|8|@]|D|@]|E|$]]|$1|Z|3|-4|5|6|7|1G|8|@]|D|@]|E|$]]]|10|$]]

When i want to remove some unused image with name <code>&quot;&lt;none&gt;&quot;</code> in docker i face with the problem <code>unable to delete a354bbc7c9b7 (cannot be forced) - image has dependent child images</code>.So for solving this problem:
<blockquote>
sudo docker ps -a
</blockquote>
<pre><code>CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
01ee1276bbe0 lizard:1 &quot;/bin/sh -c 'java ...&quot; About an hour ago Exited (1) About an hour ago objective_lewin
49d73d8fb023 javaapp:latest &quot;/usr/bin/java -ja...&quot; 19 hours ago Up 19 hours 0.0.0.0:8091-&gt;8091/tcp pedantic_bell
405fd452c788 javaapp:latest &quot;/usr/bin/java -ja...&quot; 19 hours ago Created infallible_varahamihira
532257a8b705 javaapp:latest &quot;/usr/bin/java -ja...&quot; 19 hours ago Created demo-default
9807158b3fd5 javaapp:latest &quot;/usr/bin/java -ja...&quot; 19 hours ago Created xenodochial_kilby
474930241afa jenkins &quot;/bin/tini -- /usr...&quot; 13 days ago Up 4 days 0.0.0.0:8080-&gt;8080/tcp, 0.0.0.0:50000-&gt;50000/tcp myjenkins
563d8c34682f mysql/mysql-server:latest &quot;/entrypoint.sh my...&quot; 3 weeks ago Up 4 days (healthy) 0.0.0.0:3306-&gt;3306/tcp, 33060/tcp mymysql
b4ca73d45d20 phpmyadmin/phpmyadmin &quot;/run.sh phpmyadmin&quot; 4 weeks ago Exited (0) 3 weeks ago phpmyadmin
</code></pre>
you can see that i have several Images with name javaapp:latest and different container name. So, i killed and remove all container of &quot;javaapp:latest&quot; container with:
<blockquote>
sudo docker stop &quot;containerName&quot;
sudo docker rm &quot;containrName&quot;
</blockquote>
Then
<blockquote>
sudo docker rmi -f &quot;imageId&quot;
</blockquote>
So i can remove all the images with name <code>&quot;&lt;none&gt;&quot;</code>
goodluck

blocks|key|1211858|text|正如解释过的这里一样，我使用了以下方法来识别和删除依赖的图像，|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1211859|image_id=123456789012

docker+images+-a+-q+--filter+since=$image_id+%7C
xargs+docker+inspect+--format='{{.Id}}+{{.Parent}}'|code-block|syntax|javascript|1211860|您将看到类似于此的输出：|1211861|sha256:f7ef19862215ec0bf7a6b103504d213e1c001691703808f4154689cfbb5f14f9+sha256:a7d2efad2847bd10e5223980ed80f5781c716eddbf6131a3cf97614e7f2db97f
sha256:03690ae141346203959d0ae1b3e8d34b7a4232095d774af57dda6282fce99cc4+sha256:5713074659bb5352496ea680a903eba2f66e0495538c9db37336f4ba92994ea8
sha256:311f587811942d328edc52e5953d794eb9b81fe392512080d9fc1d350a6b2024+sha256:aa674f7f2621946db257720c378377b8714739d20879542d875b84c53b59bc75|1211862|然后，您可以逐个删除这些图像如下：|1211863|docker+image+rm+f7ef19862215ec0bf7a6b103504d213e1c001691703808f4154689cfbb5f14f9|1211864|输出与下面类似的内容：|1211865|Untagged:+prathap/cognitive_robotics_gpu:v1
Untagged:+prathap/cognitive_robotics_gpu@sha256:db6e7543a13e9a96241c985b9b3145b8fd65effb68c183301385b495875f1a5a
Deleted:+sha256:03690ae141346203959d0ae1b3e8d34b7a4232095d774af57dda6282fce99cc4
Deleted:+sha256:263f655670436758f8e3f23f31170083fc8d60c4eebe01a5b3fda1e73bed3ad1|1211866|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/36584122/how-to-get-the-list-of-dependent-child-images-in-docker^0|6|2|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]]|C|$]]|$1|D|3|E|5|F|7|16|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|17|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|18|8|@]|9|@]|C|$G|H]]|$1|M|3|N|5|6|7|19|8|@]|9|@]|C|$]]|$1|O|3|P|5|F|7|1A|8|@]|9|@]|C|$G|H]]|$1|Q|3|R|5|6|7|1B|8|@]|9|@]|C|$]]|$1|S|3|T|5|F|7|1C|8|@]|9|@]|C|$G|H]]|$1|U|3|-4|5|6|7|1D|8|@]|9|@]|C|$]]]|V|$W|$5|X|Y|Z|C|$10|11]]]]

As explained <a href="https://stackoverflow.com/questions/36584122/how-to-get-the-list-of-dependent-child-images-in-docker">here</a>, I used the following way to identify dependent images and delete them,
<pre><code>image_id=123456789012

docker images -a -q --filter since=$image_id |
xargs docker inspect --format='{{.Id}} {{.Parent}}'
</code></pre>
You would see something similar to this as the output:
<pre><code>sha256:f7ef19862215ec0bf7a6b103504d213e1c001691703808f4154689cfbb5f14f9 sha256:a7d2efad2847bd10e5223980ed80f5781c716eddbf6131a3cf97614e7f2db97f
sha256:03690ae141346203959d0ae1b3e8d34b7a4232095d774af57dda6282fce99cc4 sha256:5713074659bb5352496ea680a903eba2f66e0495538c9db37336f4ba92994ea8
sha256:311f587811942d328edc52e5953d794eb9b81fe392512080d9fc1d350a6b2024 sha256:aa674f7f2621946db257720c378377b8714739d20879542d875b84c53b59bc75
</code></pre>
Then you can delete those images one by one as below:
<pre><code>docker image rm f7ef19862215ec0bf7a6b103504d213e1c001691703808f4154689cfbb5f14f9
</code></pre>
Output something similar to bellow:
<pre><code>Untagged: prathap/cognitive_robotics_gpu:v1
Untagged: prathap/cognitive_robotics_gpu@sha256:db6e7543a13e9a96241c985b9b3145b8fd65effb68c183301385b495875f1a5a
Deleted: sha256:03690ae141346203959d0ae1b3e8d34b7a4232095d774af57dda6282fce99cc4
Deleted: sha256:263f655670436758f8e3f23f31170083fc8d60c4eebe01a5b3fda1e73bed3ad1
</code></pre>

blocks|key|1620169|text|扩展@Nguyen提供的答案-这个函数可以添加到您的.bashrc等，然后从命令行调用，以帮助清理任何.bashrc错误.|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1620170|您可以自己运行该函数，如果docker+ps失败，它将使用sudo运行docker命令，并提示您输入密码。|1620171|不是删除任何正在运行的容器的图像吗？|BOLD|1620172|docker_rmi_dependants+()+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
{+
++DOCKER=docker
++[+docker+ps+>/dev/null+2>&1+]+%7C%7C+DOCKER="sudo+docker"

++echo+"Docker:+${DOCKER}"

++for+n+in+$(${DOCKER}+images+%7C+awk+'$2+==+"<none>"+{print+$3}');
++do++
++++echo+"ImageID:+$n";
++++${DOCKER}+inspect+--format='{{.Id}}+{{.Parent}}'+$(${DOCKER}+images+--filter+since=$n+-q);
++done;

++${DOCKER}+rmi+$(${DOCKER}+images+%7C+awk+'$2+==+"<none>"+{print+$3}')
}|code-block|syntax|javascript|1620173|我的.bashrc文件里也有这个.|1620174|docker_rm_dangling+()++
{+
++DOCKER=docker
++[+docker+ps+>/dev/null+2>&1+]+%7C%7C+DOCKER="sudo+docker"

++echo+"Docker:+${DOCKER}"

++${DOCKER}+images+-f+dangling=true+2>&1+>+/dev/null+&&+YES=$?;++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++if+[+$YES+-eq+1+];+then
++++read+-t+30+-p+"Press+ENTER+to+remove,+or+CTRL-C+to+quit.";
++++${DOCKER}+rmi+$(${DOCKER}+images+-f+dangling=true+-q);
++else
++++echo+"Nothing+to+do...+all+groovy!";
++fi++
}|1620175|与以下方面合作：|1620176|$+docker+--version+
Docker+version+17.05.0-ce,+build+89658be|1620177|entityMap^0|Q|7|1F|7|0|D|9|T|4|Z|6|0|0|2|0|0|2|7|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|14|8|@$9|15|A|16|B|C]|$9|17|A|18|B|C]|$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1B|8|@$9|1C|A|1D|B|J]]|D|@]|E|$]]|$1|K|3|L|5|M|7|1E|8|@]|D|@]|E|$N|O]]|$1|P|3|Q|5|6|7|1F|8|@$9|1G|A|1H|B|C]]|D|@]|E|$]]|$1|R|3|S|5|M|7|1I|8|@]|D|@]|E|$N|O]]|$1|T|3|U|5|6|7|1J|8|@]|D|@]|E|$]]|$1|V|3|W|5|M|7|1K|8|@]|D|@]|E|$N|O]]|$1|X|3|-4|5|6|7|1L|8|@]|D|@]|E|$]]]|Y|$]]

Expanding on the answer provided by @Nguyen - this function can be added to your <code>.bashrc</code> etc and then called from the commandline to help clean up any <code>image has dependent child images</code> errors...

You can run the function as yourself, and if a <code>docker ps</code> fails, then it will run the <code>docker</code> command with <code>sudo</code> and prompt you for your password.

Does NOT delete images for any running containers!

<pre><code>docker_rmi_dependants () 
{ 
 DOCKER=docker
 [ docker ps &gt;/dev/null 2&gt;&amp;1 ] || DOCKER="sudo docker"

 echo "Docker: ${DOCKER}"

 for n in $(${DOCKER} images | awk '$2 == "&lt;none&gt;" {print $3}');
 do 
 echo "ImageID: $n";
 ${DOCKER} inspect --format='{{.Id}} {{.Parent}}' $(${DOCKER} images --filter since=$n -q);
 done;

 ${DOCKER} rmi $(${DOCKER} images | awk '$2 == "&lt;none&gt;" {print $3}')
}
</code></pre>

I also have this in my <code>.bashrc</code> file...

<pre><code>docker_rm_dangling () 
{ 
 DOCKER=docker
 [ docker ps &gt;/dev/null 2&gt;&amp;1 ] || DOCKER="sudo docker"

 echo "Docker: ${DOCKER}"

 ${DOCKER} images -f dangling=true 2&gt;&amp;1 &gt; /dev/null &amp;&amp; YES=$?; 
 if [ $YES -eq 1 ]; then
 read -t 30 -p "Press ENTER to remove, or CTRL-C to quit.";
 ${DOCKER} rmi $(${DOCKER} images -f dangling=true -q);
 else
 echo "Nothing to do... all groovy!";
 fi 
}
</code></pre>

Works with:

<pre><code>$ docker --version 
Docker version 17.05.0-ce, build 89658be
</code></pre>

blocks|key|1211577|text|我也有这个问题，我可以用下面的命令来解决问题。这可能是因为，图像的容器正在运行或退出，所以在删除图像之前，您需要删除容器|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1211578|docker+-a+-f+status=exited+:此命令显示所有已退出的容器，然后复制容器Id，然后在命令下面运行以删除容器|1211579|docker+#+child+:这个命令删除容器--这可能是提到“图像有依赖的子映像”的问题|1211580|然后尝试使用以下命令删除图像|1211581|docker+rmi+#ImageId|1211582|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

I also got this issue, I could resolve issue with below commands. this may be cause, the image's container is running or exit so before remove image you need to remove container

docker ps -a -f status=exited : this command shows all the exited containers so then copy container Id and then run below commands to remove container

docker rm #containerId : this command remove container this may be issue that mention "image has dependent child images"

Then try to remove image with below command

docker rmi #ImageId

blocks|key|1211642|text|我有这个问题，这里没有一个简短的答案有效，甚至在上面@tudor提到的页面中也是如此。我想在这里分享一下我是如何摆脱这些图像的。我想出了一个想法，即依赖的图像必须是父映像大小的>=，这有助于识别它，这样我们就可以删除它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1211643|我列出了这些图像的大小，以确定是否能识别出任何相关性：|1211644|docker+images+--format+'{{.Size}}\t{{.Repository}}\t{{.Tag}}\t{{.ID}}'+%7C+sort+-h+-r+%7C+column+-t|code-block|syntax|javascript|1211645|这样做，是使用一些特殊的格式设置从码头，首先定位图像大小列，然后运行一个人类可读的排序以相反的顺序。然后我还原易读的列。|1211646|然后我查看了<none>容器，并将列表中的第一个容器与类似的大小进行了匹配。我在这个映像上执行了一个简单的docker+rmi+<image:tag>，所有的<none>子映像都跟着执行。|offset|length|style|CODE|1211647|当我第一次开始玩码头时，所有的子图像的问题图像实际上都是该死的myrepo/getstarted-lab+我用过的图像。这是因为我从创建链的第一个测试映像中创建了一个新的映像。|1211648|希望这能对其他人有所帮助。|1211649|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.docker.com/get-started/^0|0|0|0|0|6|6|1H|M|27|6|0|V|L|1H|6|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|14|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|15|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|16|8|@$M|17|N|18|O|P]|$M|19|N|1A|O|P]|$M|1B|N|1C|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1D|8|@$M|1E|N|1F|O|P]]|9|@$M|1G|N|1H|1|1I]]|A|$]]|$1|S|3|T|5|6|7|1J|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]]]

I had this issue and none of the short answers here worked, even in the page mentioned by @tudor above. I thought I would share here how I got rid of the images. I came up with the idea that dependent images must be >= the size of the parent image, which helps identify it so we can remove it.

I listed the images in size order to see if I could spot any correlations: 

<pre><code>docker images --format '{{.Size}}\t{{.Repository}}\t{{.Tag}}\t{{.ID}}' | sort -h -r | column -t
</code></pre>

What this does, is use some special formatting from docker to position the image size column first, then run a human readable sort in reverse order. Then I restore the easy-to-read columns.

Then I looked at the <code>&lt;none&gt;</code> containers, and matched the first one in the list with a similar size. I performed a simple <code>docker rmi &lt;image:tag&gt;</code> on that image and all the <code>&lt;none&gt;</code> child images went with it.

The problem image with all the child images was actually the damn <code>myrepo/getstarted-lab</code> <a href="https://docs.docker.com/get-started/" rel="nofollow noreferrer">image I used</a> when I first started playing with docker. It was because I had created a new image from the first test image which created the chain.

Hopefully that helps someone else at some point.

blocks|key|1620197|text|尝试删除图像id：b721d1cdaac7|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1620198|+docker+rmi+b721d1cdaac7+-f|code-block|syntax|javascript|1620199|响应:来自守护进程的错误响应:冲突:无法删除b721d1cdaac7+(不能强制)-图像有依赖的子图像|blockquote|1620200|删除所有子图像|1620201|docker+image+rm+$(docker+images+--filter+since=b721d1cdaac7+-q)+-f|1620202|entityMap^0|9|C|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|W|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|M|7|X|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|Y|8|@]|D|@]|E|$]]|$1|P|3|Q|5|H|7|Z|8|@]|D|@]|E|$I|J]]|$1|R|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|S|$]]

Trying to delete image id : <code>b721d1cdaac7</code>
<pre><code> docker rmi b721d1cdaac7 -f
</code></pre>
<blockquote>
Response : Error response from daemon: conflict: unable to delete b721d1cdaac7 (cannot be forced) - image has dependent child images
</blockquote>
To delete all child images
<pre><code>docker image rm $(docker images --filter since=b721d1cdaac7 -q) -f
</code></pre>

blocks|key|1211584|text|强制删除图像列表(例如，不包括版本10+)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1211585|-v+version10+>+images.txt+&+for在$(+awk+-F“'{print+$3}‘/root/images.txt+)；do码头rmi+-f+$img；|blockquote|1211586|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|H|8|@]|9|@]|A|$]]|$1|E|3|-4|5|6|7|I|8|@]|9|@]|A|$]]]|F|$]]

Force deleting a list of images (exclude version 10, for example) 

<blockquote>
 docker images | grep version | grep -v version10 > images.txt &amp;&amp; for
 img in $( awk -F" " '{print $3}' /root/images.txt ) ; do docker rmi
 -f $img; done
</blockquote>

blocks|key|1214526|text|假设我们有一个Dockerfile|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1214527|FROM+ubuntu:trusty
CMD+ping+localhost|code-block|syntax|javascript|1214528|我们在没有标记或命名的情况下构建图像。|1214529|docker+build+.|1214530|现在我们有一个成功的报告“成功地构建了57ca5ce94d04”，如果我们看到了码头图像|1214531|REPOSITORY++++++++++TAG+++++++++++++++++IMAGE+ID++++++++++++CREATED+++++++++++++SIZE
<none>++++++++++++++<none>++++++++++++++57ca5ce94d04++++++++18+seconds+ago++++++188MB
ubuntu++++++++++++++trusty++++++++++++++8789038981bc++++++++11+days+ago+++++++++188MB|1214532|我们需要首先删除docker+rmi+57ca5ce94d04|offset|length|style|CODE|1214533|紧接着是|1214534|docker+rmi+8789038981bc|1214535|由该图像将被移除！|1214536|按某人的建议强行移走所有的东西|1214537|docker+rmi+$(docker+images+-q)+-f|1214538|entityMap^0|0|0|0|0|0|0|8|N|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|17|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|18|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|19|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|1A|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|1B|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|1C|8|@$Q|1D|R|1E|S|T]]|9|@]|A|$]]|$1|U|3|V|5|6|7|1F|8|@]|9|@]|A|$]]|$1|W|3|X|5|D|7|1G|8|@]|9|@]|A|$E|F]]|$1|Y|3|Z|5|6|7|1H|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|1I|8|@]|9|@]|A|$]]|$1|12|3|13|5|D|7|1J|8|@]|9|@]|A|$E|F]]|$1|14|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]]|15|$]]

Suppose we have a Dockerfile

<pre><code>FROM ubuntu:trusty
CMD ping localhost
</code></pre>

We build image from that without TAG or naming

<pre><code>docker build .
</code></pre>

Now we have a success report "Successfully built 57ca5ce94d04"
If we see the docker images 

<pre><code>REPOSITORY TAG IMAGE ID CREATED SIZE
&lt;none&gt; &lt;none&gt; 57ca5ce94d04 18 seconds ago 188MB
ubuntu trusty 8789038981bc 11 days ago 188MB
</code></pre>

We need to first remove the 
<code>docker rmi 57ca5ce94d04</code>

Followed by 

<pre><code>docker rmi 8789038981bc
</code></pre>

By that image will be removed!

A forced removal of all as suggested by someone

<pre><code>docker rmi $(docker images -q) -f
</code></pre>

blocks|key|2373304|text|只需简单地使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2373305|docker+rmi+<image:tag>+-f|code-block|syntax|javascript|2373306|例如：|2373307|docker+rmi+ubuntu:latest+-f+|2373308|将删除图像名为ubuntu的标记名为latest，-f用于强制删除。|offset|length|style|CODE|2373309|对我来说很管用|2373310|entityMap^0|0|0|0|0|7|6|I|6|P|2|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|Y|8|@$M|Z|N|10|O|P]|$M|11|N|12|O|P]|$M|13|N|14|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|15|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|T|$]]

Just simply use:
<pre><code>docker rmi &lt;image:tag&gt; -f
</code></pre>
for example:
<pre><code>docker rmi ubuntu:latest -f 
</code></pre>
will remove image name <code>ubuntu</code> with tag name <code>latest</code> and <code>-f</code> is for forcefully removal.
it worked for me

blocks|key|1620341|text|确保您没有达到的利率限制错误，如果背后的企业代理。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1620342|如果偶然地，您支持一个公司代理并使用Windows，您可能需要尝试这个简单的修补程序。我发现这里有几个回答很有帮助。然而，即使在运行了一个docker+image+prune和其他命令之后，我也发现了一个可爱的错误(和根本原因)，这个错误以前被掩盖了：“toomanyrequest:您已经达到了拉速限制.”|CODE|1620343|修复。|1620344|打开Windows终端/DOS提示符并输入：|ordered-list-item|1620345|ipconfig/release|unordered-list-item|1620346|..。|1620347|ipconfig/renew|1620348|这可能只会为你节省一个电话/票与它。;)|1620349|entityMap^0|7|7|0|1X|I|0|0|0|0|G|0|0|0|E|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|11|8|@$9|12|A|13|B|H]]|D|@]|E|$]]|$1|I|3|J|5|6|7|14|8|@]|D|@]|E|$]]|$1|K|3|L|5|M|7|15|8|@]|D|@]|E|$]]|$1|N|3|O|5|P|7|16|8|@$9|17|A|18|B|H]]|D|@]|E|$]]|$1|Q|3|R|5|P|7|19|8|@]|D|@]|E|$]]|$1|S|3|T|5|P|7|1A|8|@$9|1B|A|1C|B|H]]|D|@]|E|$]]|$1|U|3|V|5|6|7|1D|8|@]|D|@]|E|$]]|$1|W|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]]|X|$]]

Assure you haven't hit the rate-limit error if behind a corporate proxy.
If, by chance, you're behind a corporate proxy and using Windows, you may want to try this simple fix. I found several responses here helpful. However, even after running a <code>docker image prune</code> and other commands, I uncovered the lovely error (and root cause), which was previously masked: &quot;toomanyrequests: You have reached your pull rate limit...&quot;
Fix.
<ol>
<li>Open a Windows Terminal/DOS prompt and enter:</li>
</ol>
<ul>
<li><code>ipconfig/release</code></li>
<li>[...]</li>
<li><code>ipconfig/renew</code></li>
</ul>
This might just save you a call/ticket with IT. ;)

blocks|key|2373201|text|映像层：存储库通常被称为图像或容器映像，但实际上它们是由一个或多个层组成的。存储库中的图像层在父-子关系中连接在一起。每个图像层表示自身和父层之间的变化。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2373202|码头构建模式使用继承。这意味着版本i依赖于版本i-1。因此，我们必须删除版本i%2B1，以便能够删除版本i。这是一个简单的依赖关系。|CODE|2373203|如果您想删除除最后一个(最新更新的)和第一个(基本)之外的所有图像，那么我们可以使用下面的docker+save命令导出最后一个(最新的)图像。|2373204|docker+save+-o+<output_file>+<your_image-id>+%7C+gzip+<output_file>.tgz|code-block|syntax|javascript|2373205|然后，现在，使用图像id删除所有图像，如下所示。|2373206|docker+rm+-f+<image-id+i>+%7C+docker+rm+-f+<image+i-1>+%7C+docker+rm+-f+<image-id+i-2>+...+<docker+rm+-f+<image-id+i-k>+#+where+i-k+=+1|2373207|现在，加载保存的tgz映像，如下所示。|2373208|gzip+-c+<output_file.tgz>+%7C+docker+load|2373209|请参见使用docker+-q加载的映像的图像id。它没有标签和名字。您可以简单地更新标签和名称，如下所示。|2373210|docker+tag+<image_id>+group_name/name:tag|2373211|entityMap^0|0|4|0|8|2|H|1|N|3|12|3|1E|1|0|19|B|0|0|8|4|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@$9|14|A|15|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|16|8|@$9|17|A|18|B|C]|$9|19|A|1A|B|H]|$9|1B|A|1C|B|H]|$9|1D|A|1E|B|H]|$9|1F|A|1G|B|H]]|D|@]|E|$]]|$1|I|3|J|5|6|7|1H|8|@$9|1I|A|1J|B|H]]|D|@]|E|$]]|$1|K|3|L|5|M|7|1K|8|@]|D|@]|E|$N|O]]|$1|P|3|Q|5|6|7|1L|8|@$9|1M|A|1N|B|C]]|D|@]|E|$]]|$1|R|3|S|5|M|7|1O|8|@]|D|@]|E|$N|O]]|$1|T|3|U|5|6|7|1P|8|@]|D|@]|E|$]]|$1|V|3|W|5|M|7|1Q|8|@]|D|@]|E|$N|O]]|$1|X|3|Y|5|6|7|1R|8|@]|D|@]|E|$]]|$1|Z|3|10|5|M|7|1S|8|@]|D|@]|E|$N|O]]|$1|11|3|-4|5|6|7|1T|8|@]|D|@]|E|$]]]|12|$]]

Image Layer: Repositories are often referred to as images or container images, but actually they are made up of one or more layers. Image layers in a repository are connected together in a parent-child relationship. Each image layer represents changes between itself and the parent layer.

The docker building pattern uses inheritance. It means the version <code>i</code> depends on version <code>i-1</code>. So, we must delete the version <code>i+1</code> to be able to delete version <code>i</code>. This is a simple dependency. 

If you wanna delete all images except the last one (the most updated) and the first (base) then we can export the last (the most updated one) using <code>docker save</code> command as below. 

<pre><code>docker save -o &lt;output_file&gt; &lt;your_image-id&gt; | gzip &lt;output_file&gt;.tgz
</code></pre>

Then, now, delete all the images using image-id as below. 

<pre><code>docker rm -f &lt;image-id i&gt; | docker rm -f &lt;image i-1&gt; | docker rm -f &lt;image-id i-2&gt; ... &lt;docker rm -f &lt;image-id i-k&gt; # where i-k = 1
</code></pre>

Now, load your saved tgz image as below.

<pre><code>gzip -c &lt;output_file.tgz&gt; | docker load
</code></pre>

see the image-id of your loaded image using docker ps -q. It doesn't have tag and name. You can simply update tag and name as done below. 

<pre><code>docker tag &lt;image_id&gt; group_name/name:tag
</code></pre>

blocks|key|2373156|text|你可以这么做：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2373157|sha256:4ed13257bb5512b975b316ef482592482ca54018a7728ea1fc387e873a68c358删除:+sha256:4a478ca02e8d2336595dcbed9c4ce034cd15f01229733e7d93a83fbb3a9026d3已删除:+sha256:96df41d1ce6065cf75d05873fb1f9ea9fed0ca86addcfcec7722200ed3484c69已删除:+sha256:d95efe864c7096c38757b80fddad12819fffd68ac3cc73333ebffaa42385fded|2373158|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

you can just do this:

➜ ~ sudo docker rmi 4ed13257bb55 -f
Deleted: sha256:4ed13257bb5512b975b316ef482592482ca54018a7728ea1fc387e873a68c358
Deleted: sha256:4a478ca02e8d2336595dcbed9c4ce034cd15f01229733e7d93a83fbb3a9026d3
Deleted: sha256:96df41d1ce6065cf75d05873fb1f9ea9fed0ca86addcfcec7722200ed3484c69
Deleted: sha256:d95efe864c7096c38757b80fddad12819fffd68ac3cc73333ebffaa42385fded

I am trying

<pre><code>docker rmi c565603bc87f
</code></pre>

Error:

<blockquote>
 Error response from daemon: conflict: unable to delete c565603bc87f
 (cannot be forced) - image has dependent child images
</blockquote>

So i can't delete image even with -f flag. How to delete image then and all of its children ?

Linux and docker version: 

uname -a
Linux goracio-pc 4.4.0-24-generic #43-Ubuntu SMP Wed Jun 8 19:27:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

docker version
Client:
Version: 1.11.2
API version: 1.23
Go version: go1.5.4
Git commit: b9f10c9
Built: Wed Jun 1 22:00:43 2016
OS/Arch: linux/amd64

Server:
Version: 1.11.2
API version: 1.23
Go version: go1.5.4
Git commit: b9f10c9
Built: Wed Jun 1 22:00:43 2016
OS/Arch: linux/amd64

Can’t delete docker image with dependent child images

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我在努力docker rmi c565603bc87f错误：来自守护进程的错误响应:冲突:无法删除c565603bc87f (不能强制)-图像有依赖的子映像因此，即使使用-f标志，我也不能删除图像。如何删除图像然后和它的所有子代？Linux和docker版本：-a Linux goracio-pc 4.4.0-24-通用#43-Ubuntu WedJun8 19:27:37 UTC 2016 x8

问无法删除带有依赖子映像的停靠器图像
EN

回答 25

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法删除带有依赖子映像的停靠器图像EN

回答 25

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法删除带有依赖子映像的停靠器图像
EN