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)

  • FATA[0000] Cannot connect to the Docker daemon. Is 'docker -d' running on this host?
  • multiple docker clients on the same machine
  • Elasticsearch 2.4 nodes does not form cluster with ConnectTransportException
  • Docker forever in “Docker is starting..” at windows task
  • Docker: cant send data from logstash container to Kafka container
  • Running VNCserver on docker container
  • Looking at the comments I don’t get the difference between the two. Aren’t all untagged images also deleted?

  • Boot2Docker: how to access container with Bridged Networking
  • Vagrant and NGINX only works on ports other than 80
  • proxy_pass https in a Docker Container
  • How to access web app live inside docker in docker
  • docker-py: attach to network before starting the container
  • Creating an ng-cli container in docker not working
  • 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.