Go to My Images, click on Delete Tag, and image should be deleted.
Image is not being deleted after taking steps to delete.
This used to work before upgrading to version 0.17.0.
Can you open the developer console and see if there are any errors being posted?
If you do a docker image ls do you still see the image as well?
Here is what I caught in the console when I click on Delete Tag. Doing docker image ls shows the image remaining. I can also replicate this behavior on a different Mac.

I should add that I can still do docker rmi instance-id, which does remove the image.
can you show the image names that you were trying to delete and the tags that were associated with them?
Here are some screenshots. It happens with all of the images. Not just a specific one.


Can you provide the output of the following?
$ docker inspect $(docker image ls -q)
I'm trying to see why it complains about the repo tags missing, when you have them
Here is the output from the only image I have right now.
[
{
"Id": "sha256:03b4557ad7b98859ac39aee048ce400a664de81cfa625fd7dfa94e61ac7c1947",
"RepoTags": [
"kitematic/hello-world-nginx:latest"
],
"RepoDigests": [
"kitematic/hello-world-nginx@sha256:ec0ca6dcb034916784c988b4f2432716e2e92b995ac606e080c7a54b52b87066"
],
"Parent": "",
"Comment": "",
"Created": "2015-06-16T05:11:24.935216949Z",
"Container": "fa94ba2c449526ffa7851c9c74613c7b5d3ad6c1f302ba7c09343866c58da51d",
"ContainerConfig": {
"Hostname": "02e2289f4b2c",
"Domainname": "",
"User": "",
"AttachStdin": false,
"AttachStdout": false,
"AttachStderr": false,
"ExposedPorts": {
"80/tcp": {}
},
"Tty": false,
"OpenStdin": false,
"StdinOnce": false,
"Env": null,
"Cmd": [
"/bin/sh",
"-c",
"#(nop) CMD [\"sh\" \"/start.sh\"]"
],
"Image": "fa8fefb0eeccc8e9ff15966f8f0e10246edd8b52247e8f5fcc56acd313071ee1",
"Volumes": {
"/website_files": {}
},
"WorkingDir": "",
"Entrypoint": null,
"OnBuild": null,
"Labels": {}
},
"DockerVersion": "1.6.2",
"Author": "",
"Config": {
"Hostname": "02e2289f4b2c",
"Domainname": "",
"User": "",
"AttachStdin": false,
"AttachStdout": false,
"AttachStderr": false,
"ExposedPorts": {
"80/tcp": {}
},
"Tty": false,
"OpenStdin": false,
"StdinOnce": false,
"Env": null,
"Cmd": [
"sh",
"/start.sh"
],
"Image": "fa8fefb0eeccc8e9ff15966f8f0e10246edd8b52247e8f5fcc56acd313071ee1",
"Volumes": {
"/website_files": {}
},
"WorkingDir": "",
"Entrypoint": null,
"OnBuild": null,
"Labels": {}
},
"Architecture": "amd64",
"Os": "linux",
"Size": 7912576,
"VirtualSize": 7912576,
"GraphDriver": {
"Name": "aufs",
"Data": null
},
"RootFS": {
"Type": "layers",
"Layers": [
"sha256:461f75075df2a334108df11b185363d2afda21517fda5ffb10852020e7639b7b",
"sha256:6a15a6c08ef640f9c00b55152f2592ac292e80f1f90d0eefdafcb23fac03025f",
"sha256:e66f0ebc2eefae7ee2161021ff63f24bb0f9fed26a5e8809963b270a26955fa1",
"sha256:9e8c93c7ea7e4c25b8bf1d3d972528ddb2745c3f26fbd74a5c676d72f86486f0",
"sha256:86882fc1175f1b969342fc3f0b50ff6e55aaf6d87ae1d6e6e56661b11ccb3f16",
"sha256:15235e62986412784221a17c6ae3d235fd97ff23f4dd4ab60866e5bc882a4c86",
"sha256:fb85701f3991c06d50a7ad127f0d0e7d316768cb37efa844e4f7d310f0429cde",
"sha256:b11278aeb507249b95588ed4df8feff2635cc403ba279d6eacec6c755fea09a3",
"sha256:f19fb69b288a59e18a570ae958748788b599ff36648ea2d7b2ffcfc92a7f0bd4",
"sha256:3f47ff4545884394ce745ad30f0646c110d6a457729cd468b169e404fdff80b0",
"sha256:b51acdd3ef48a22295dfe3b824b0edcb2917da103828d83353d5ec91b155c929",
"sha256:5f70bf18a086007016e948b04aed3b82103a36bea41755b6cddfaf10ace3c6ef",
"sha256:5f70bf18a086007016e948b04aed3b82103a36bea41755b6cddfaf10ace3c6ef",
"sha256:5f70bf18a086007016e948b04aed3b82103a36bea41755b6cddfaf10ace3c6ef"
]
}
}
]
I'm unable to replicate this locally, unfortunately - I'll keep an eye on it.
Sounds good. I've also tried removing Docker and Docker Toolbox, but the same thing happens after a reinstall.
Here the same problem, can't delete the images
Was finally able to replicate this issue - Seems that the amount of dangling images increased and are now causing some issues.
I've added a fix to disregard the dangling images from the removal process, preventing the error from happening.
see: https://github.com/docker/kitematic/pull/2726
Version 0.17.1 seems to have fixed this issue.