What is the difference between an untaggedImage & deletedImage in the docker source?

The docker source defines a struct to hold deleted images when running docker image prune or docker system prune:

type ImageDeleteResponseItem struct {

    // The image ID of an image that was deleted
    Deleted string `json:"Deleted,omitempty"`

    // The image ID of an image that was untagged
    Untagged string `json:"Untagged,omitempty"`

(source code link)

  • VOLUME command in docker image is using custom-volume driver
  • Cannot connect to the Docker daemon on macOS
  • Gitlab Docker container behind reverse Proxy
  • Keep Docker running when shell script exits
  • Tagging docker images and adding variables in docker-compose
  • Sharing a Docker container directory which serves as a mount point
  • Looking at the comments I don’t get the difference between the two. Aren’t all untagged images also deleted?

  • version control, apt (and Docker)
  • Android build fails in Ubuntu Docker container when Gradle runs transformClasses
  • Kubernetes: how to debug CrashLoopBackOff
  • How do I use the IP address instead of hostname in Eureka?
  • Is second value required when mapping ports in docker-compose file?
  • Using docker-compose 1.8 bundle with Swarm 1.12
  • One Solution collect form web for “What is the difference between an untaggedImage & deletedImage in the docker source?”

    It’s not necessary that untagging deletes an image. If you have an image tagged with more than one tag. It’ll delete the tag and image will be there with the other tag.

    docker rmi first-tag will remove the first-tag but will still persist the image with second-tag. It would have been disastrous if it deleted the whole image whenever we tried to remove the tag.

    You can see here for more.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.