The docs now explain that images with repo:tag as <none>:<none> are dangling images.

Signed-off-by: Sambuddha Basu <sambuddhabasu1@gmail.com>
Upstream-commit: 93ce6fd9f5
Component: cli
This commit is contained in:
Sambuddha Basu
2017-06-02 00:07:19 +00:00
committed by Tibor Vass
parent 562373192d
commit 5dd1c0387f
@@ -136,9 +136,9 @@ The currently supported filters are:
This will display untagged images, that are the leaves of the images tree (not
intermediary layers). These images occur when a new build of an image takes the
`repo:tag` away from the image ID, leaving it untagged. A warning will be issued
if trying to remove an image when a container is presently using it.
By having this flag it allows for batch cleanup.
`repo:tag` away from the image ID, leaving it as `<none>:<none>` or untagged.
A warning will be issued if trying to remove an image when a container is presently
using it. By having this flag it allows for batch cleanup.
Ready for use by `docker rmi ...`, like: