Docker remove TAG images

Question

root@server:~# docker images -a        
REPOSITORY              TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
<none>                  <none>              5e2dfc857e73        5 days ago          261.6 MB
<none>                  <none>              d053e988f23d        5 days ago          261.6 MB
<none>                  <none>              1d5d4a2d89eb        5 days ago          261.6 MB
<none>                  <none>              ea0d189fdb19        5 days ago          100.5 MB
<none>                  <none>              26c6175962b3        5 days ago          100.5 MB
<none>                  <none>              73d5cec4a0b3        5 days ago          100.5 MB
<none>                  <none>              e19590e1bac1        5 days ago          100.5 MB

I've tried the following:

docker rmi $(docker images | grep "^<none>" | awk "{print $3}")

And the following:

docker rmi $(docker images -f "dangling=true" -q)

Get the following error:

docker: "rmi" requires a minimum of 1 argument.
See 'docker rmi --help'.

Usage:  docker rmi [OPTIONS] IMAGE [IMAGE...]

Remove one or more images

It's a bit late but I have to add this comment for other users. If you use Windows Command Prompt, this won't work. Because Command Prompt doesn't support inner functions. Try the exact lines with Windows PowerShell — er-han, Jun 19 '17 at 06:47
`docker rmi $(docker images -a | grep "^" | awk '{print $3}')` — Ondra Žižka, Mar 08 '18 at 00:54
@Karl Morrison: You were nearly there: just missed -a (--all) in `docker images` :) — mirekphd, Apr 18 '20 at 20:27

VonC · Accepted Answer · 2023-04-10T19:51:43.067

You can try and list only untagged images (ones with no labels, or with label with no tag):

docker images -q -a | xargs docker inspect --format='{{.Id}}{{range $rt := .RepoTags}} {{$rt}} {{end}}'|grep -v ':'

However, some of those untagged images might be needed by others.

I prefer removing only dangling images:

docker rmi $(docker images --filter "dangling=true" -q --no-trunc)

As I mentioned for for docker 1.13+ in Sept. 2016 in "How to remove old and unused Docker images", you can also do the image prune command:

docker image prune

tansadio suggests:

docker images -a | grep none | awk '{ print $3; }' | xargs docker rmi --force

But, as noted by BryanK: make sure your repository name (or one of your tag names) does not have the sequence of characters 'none' or those will match the regular expression and get removed too.

That being said, Janaka Bandara mentions in the comments:

This did not remove <none>-tagged images for me (e.g. foo/bar:<none>); I had to use docker images --digests and docker rmi foo/bar@<digest>

Janaka references "How to Remove a Signed Image with a Tag" from Paul V. Novarese:

# docker images
REPOSITORY               TAG                 IMAGE ID            CREATED             SIZE
pvnovarese/mprime        latest              459769dbc7a1        5 days ago          4.461 MB
pvnovarese/mprime        <none>              459769dbc7a1        5 days ago          4.461 MB

Diagnostic Steps

You can see the difference in these two entries if you use the --digests=true option (the untagged entry has the Docker Content Trust signature digest):

# docker images --digests=true
REPOSITORY               TAG                 DIGEST                                                                    IMAGE ID            CREATED             SIZE
pvnovarese/mprime        latest              <none>                                                                    459769dbc7a1        5 days ago          4.461 MB
pvnovarese/mprime        <none>              sha256:0b315a681a6b9f14f93ab34f3c744fd547bda30a03b55263d93861671fa33b00   459769dbc7a1        5 days ago

Note that Paul also mentions moby issue 18892:

After pulling a signed image, there is an "extra" entry (with tag <none>) in "docker images" output.
This makes it difficult to rmi the image (you have to force it, or else first delete the properly-tagged entry, or delete by digest.

This thread also proposes:

First, you need to change the tag of the specific image you want to remove.
docker tag container_id repo_name:new_tag_name

# example 
docker tag 1234567er34r davesaah/my-repo:old
Next, remove the image with the new tag created using docker rmi
docker rmi repo-name:tag

# using the previous example 
docker rmi davesaah/my-repo:old
This will remove the dangling image that has dependent child images.

This did not remove ``-tagged images for me (e.g. `foo/bar:`); I had to use `docker images --digests` and `docker rmi foo/bar@` as described at https://success.docker.com/KBase/How_to_Remove_a_Signed_Image_with_a_%3Cnone%3E_Tag — Janaka Bandara, Aug 12 '17 at 05:02
@JanakaBandara Thank you. I have included your comment in the answer (with some additional links) — VonC, Aug 12 '17 at 05:39
for me `sudo docker rmi $(docker images --filter "dangling=true" -q --no-trunc)` `Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.35/images/json?filters=%7B%22dangling%22%3A%7B%22true%22%3Atrue%7D%7D: dial unix /var/run/docker.sock: connect: permission denied "docker rmi" requires at least 1 argument. See 'docker rmi --help'. Usage: docker rmi [OPTIONS] IMAGE [IMAGE...] [flags] Remove one or more images ` — Jamie Hutber, Feb 07 '18 at 14:39
@JamieHutber "docker rmi" requires at least 1 argument. That suggests docker images --filter "dangling=true" -q --no-trunc returns nothing, meaning there is no dangling images? — VonC, Feb 07 '18 at 14:42
Thanks VonC actually it doesn't `hutber@hutber-blade /var/www/dockerfile-wizard $ sudo docker images --filter "dangling=true" -q --no-trunc sha256:c58f4e4b10b1f862d78f96e90bdf13ffe37993279d0992be46d5c15dad51421e sha256:db28e821bc3f337caf711a664bc529be5db8894dd73c5b013ad814cc1e9fc21b sha256:257936750a7d43ae77c713c2cb18342be935de7d3b8fad23d6664fc64acfe753 sha256:6b815cefeb527885b2b9dd831f7f40b05942f00d1367274833a6274154d8ce43 ` — Jamie Hutber, Feb 07 '18 at 15:58
tks, "docker image prune -f" is the official one to remove dangling none:none images — Dee, Jun 14 '20 at 00:36
Your second line was the solution for me. I'd prefer not to mess around with prune since it can erase absolutely everything I have as a docker image. — Lucas Camino, Jan 24 '23 at 02:29
@LucasCamino Good point, especially since I just edited my [`docker prune` answer](https://stackoverflow.com/a/32723127/6309) to explain why there is no "`--dry-run`" mode for those prune commands. — VonC, Jan 24 '23 at 06:47

score 143 · Answer 2 · edited Jun 15 '22 at 15:59

143

docker images -a | grep none | awk '{ print $3; }' | xargs docker rmi

You can try this simply

edited Jun 15 '22 at 15:59

Nagev

10,835
4
58
69

answered Apr 26 '18 at 10:11

tansadio

1,439
1
7
2

17

Have to add `--force` at the end. So the command will look like- `docker images | grep none | awk '{ print $3; }' | xargs docker rmi --force` – Munim Apr 17 '20 at 10:43
@MunimDibosh Just add `-f` at end of the commend from answer. – Eric Oct 29 '20 at 09:35
5

Had to add a `-a` to docker images to make it work: `docker images -a | grep none | awk '{ print $3; }' | xargs docker rmi --force`. – bappak Dec 16 '20 at 18:06
Just make sure your repository name (or one of your tag names) does not have the sequence of characters 'none' or those will match the regular expression and get removed too – BryanK Aug 08 '22 at 19:21

score 61 · Answer 3 · answered Jul 25 '17 at 11:16

docker image prune removes all dangling images (those with tag none). docker image prune -a would also remove any images that have no container that uses them.

The difference between dangling and unused images is explained in this stackoverflow thread.

score 54 · Answer 4 · answered Jan 27 '20 at 14:30

54

Just run this command:

docker image prune --filter="dangling=true"

answered Jan 27 '20 at 14:30

Ragnar

4,393
1
27
40

I started with docker image prune. however, the dangling=true removed the stubborn ones. – zerocog Sep 11 '20 at 05:41
1

This should be the correct answer @basickarl – Dirc Feb 16 '22 at 15:22

score 28 · Answer 5 · answered Jan 09 '19 at 10:49

28

According to the docker documentation you can list only untagged (dangling) images with

$ docker images -f "dangling=true"

and redirect them to docker rmi command like that:

$ docker rmi $(docker images -f "dangling=true" -q) --force

Notice -q param thats only show numeric IDs of containers.

answered Jan 09 '19 at 10:49

OzzyCzech

9,713
3
50
34

2

Isn't it similar to what I proposed in [my answer](https://stackoverflow.com/a/33913711/6309) in 2015? – VonC Jan 09 '19 at 12:13
Downvote. This is again another post which is repeating already given answers. – questionto42 Feb 17 '21 at 22:08

score 25 · Answer 6 · answered Dec 29 '21 at 07:59

25

this worked in my case

docker image rm -f $(docker images -f dangling=true -q)

answered Dec 29 '21 at 07:59

keshav swami

551
1
6
11

This worked for me. Thanks. – jedi Jan 13 '22 at 20:03

score 14 · Answer 7 · edited Nov 15 '17 at 17:07

14

Remove images which have none as the repository name using the following:

docker rmi $(docker images | grep "^<none" | awk '{print $3}')

Remove images which have none tag or repository name:

docker rmi $(docker images | grep "none" | awk '{print $3}')

edited Nov 15 '17 at 17:07

Seboudry

448
6
15

answered Apr 21 '17 at 00:10

Jerome Anthony

7,823
2
40
31

score 14 · Answer 8 · answered Apr 10 '19 at 08:54

You may check if the filter 'dangling' is no more working

$ docker images -f “dangling=true” -q
Error response from daemon: Invalid filter 'dangling'

Use docker system prune to remove the dangling images

$ docker system prune
WARNING! This will remove:
        - all stopped containers
        - all networks not used by at least one container
        - all dangling images
        - all dangling build cache
Are you sure you want to continue? [y/N]

You may use --force for not prompt for confirmation

$ docker system prune --force

score 10 · Answer 9 · edited Jan 09 '19 at 10:37

You can go docker rmi $(docker images -f "dangling=true" -q). See the images documentation for more options.

$ docker images
REPOSITORY                  TAG                 IMAGE ID            CREATED             SIZE
<none>                      <none>              94870cda569b        4 seconds ago       673MB
python                      2.7                 320a06f42b5f        10 days ago         673MB
mysql                       latest              e799c7f9ae9c        2 months ago        407MB
gcavalcante8808/semaphore   latest              86e863e11461        2 months ago        537MB
redis                       latest              e32ef7250bc1        2 months ago        184MB
rabbitmq                    3.6.9-management    7e69e14cc496        2 months ago        179MB
rabbitmq                    3.6.9               eb2e4968538a        2 months ago        179MB
jordan/rundeck              latest              6d40b57b1572        2 months ago        660MB
rabbitmq                    3.5.6-management    dbfe8d18809a        19 months ago       304MB

$ docker rmi $(docker images --format '{{.ID}}' --filter=dangling=true)
Deleted: sha256:94870cda569b8cf5f42be25af107d464c993b4502a1472c1679bf2d213b6c0a6

just doing `docker image prune --filter="dangling=true"` will work no need for the listing — Eboubaker, Mar 03 '22 at 10:03

score 10 · Answer 10 · answered Dec 09 '19 at 16:10

10

To remove all images with none we have to be sure that we removed all stopped containers which they can use run:

docker rm $(docker ps -a -q)

then we can remove all images:

docker image prune

answered Dec 09 '19 at 16:10

yevgeniy

748
9
15

score 10 · Answer 11 · answered Mar 11 '20 at 04:10

10

docker rmi --force $(docker images -q --filter "dangling=true")

answered Mar 11 '20 at 04:10

Rafaf Tahsin

7,652
4
28
45

nPcomp · Answer 12 · 2021-01-06T13:12:07.397

8

Following will remove all the <none> images

docker rmi $(docker images | grep none | awk '{print $3}')

You can force removal by changing docker rmi to docker rmi -f although I do not recommend doing that.

Some of the <none> images could be related to other images so to be on safe side don't use -f tag.

edited Jan 06 '21 at 13:12

answered Jul 26 '19 at 17:19

nPcomp

8,637
2
54
49

Jhonny Ramirez Zeballos · Answer 13 · 2021-08-22T21:16:46.363

First solution:

First delete containers that are not used.

docker ps -a | grep -v Up | awk '{ print $1; }' | xargs docker rm

Delete all containers with none tags.

docker images | grep none | awk '{ print $3; }' | xargs docker rmi

Second solution delete all with:

$ docker system prune -a


WARNING! This will remove:
- all stopped containers
- all networks not used by at least one container
- all images without at least one container associated to them
- all build cache

Are you sure you want to continue? [y/N]

score 7 · Answer 14 · edited Jun 28 '21 at 08:50

7

you can use this commend in docker :

docker image prune

and for all container:

docker container prune

edited Jun 28 '21 at 08:50

buddemat

4,552
14
29
49

answered Jun 27 '21 at 08:36

soheil raoufi

71
1
1

score 6 · Answer 15 · answered Jul 20 '18 at 10:01

6

I have found docker image prune -f most useful and I use it all the time during my day to day work, using the tag -f will not prompt for confirmation. More details here

answered Jul 20 '18 at 10:01

justjais

344
3
13

score 5 · Answer 16 · answered Jun 20 '19 at 10:00

5

docker system prune will do the trick, it removes

- all stopped containers
- all networks not used by at least one container
- all dangling images
- all dangling build cache

But use it, with the caution!

answered Jun 20 '19 at 10:00

Rajath

2,611
8
27
43

you are the boss! – topcan5 Oct 28 '20 at 21:18
Downvote. This repeats the answer of @Chetabahana which was some months earlier. – questionto42 Feb 17 '21 at 22:05

score 5 · Answer 17 · answered Sep 02 '21 at 14:03

5

The easiest solution to remove dangling (<none>) images should be:

docker image prune

Optionally you can add --force or -f to disable the prompt.

answered Sep 02 '21 at 14:03

Pascal Z.

111
2
4

score 5 · Answer 18 · answered Oct 26 '22 at 19:17

5

docker container prune to remove all stopped containers firstly, then docker image prune to remove all dangling images.

docker container prune
docker image prune

answered Oct 26 '22 at 19:17

Bruce Wen

61
1
4

this worked!! Thanks for posting. – Ezio Aug 09 '23 at 15:04

score 4 · Answer 19 · answered Jul 18 '17 at 17:57

4

Just remove the images using their IDs:

# docker rmi 5e2dfc857e73 d053e988f23d ...

answered Jul 18 '17 at 17:57

Daniel Borges

329
3
5

1

This answer is by far the simplest. – Matthew Setter Nov 10 '21 at 07:57

score 4 · Answer 20 · answered Dec 24 '19 at 02:31

4

All

Sharing the PowerShell command for windows lovers (just in case you don't have bash, grep or awk)

(docker images) -like '*<none>*' | ForEach-Object { 
  $imageid=($_ -split "\s+")[2]
  docker rmi -f $imageid
}

answered Dec 24 '19 at 02:31

Jhony Polanía

51
1

score 3 · Answer 21 · edited Nov 21 '20 at 11:02

3

100% works: docker images | grep none | awk '{print $3}' | xargs docker rmi -f

edited Nov 21 '20 at 11:02

AnhellO

855
1
14
16

answered Jul 03 '20 at 09:34

sudhir tataraju

1,159
1
14
30

score 3 · Answer 22 · answered Jul 22 '21 at 21:00

3

i've found this for windows:

powershell -Command "docker rmi $(docker images -q -f dangling=true)"

reference: https://gist.github.com/sebagomez/b00bd9e3610abab55fefe3d69f3708ad

answered Jul 22 '21 at 21:00

Francisco Duarte

71
3

ambition_sky · Answer 23 · 2022-08-22T09:25:35.200

3

docker image rm $(docker images | grep none)

edited Aug 22 '22 at 09:25

answered Aug 13 '22 at 08:29

ambition_sky

91
1
3

score 2 · Answer 24 · edited Apr 11 '20 at 08:08

2

Run the following command to remove the images with docker rmi

docker images --filter "dangling=true"

edited Apr 11 '20 at 08:08

mhovd

3,724
2
21
47

answered Apr 10 '20 at 09:25

Jatinder Dhaliwal

379
3
3

Prune the containers first so that the images aren't being "used" by stopped containers . Then delete the dangling images. – Paul Bendevis Oct 18 '21 at 13:49

score 2 · Answer 25 · answered Apr 26 '20 at 21:30

2

Remove all exited containers

docker rm $(docker container ls -a -f status=exited -q)

or remove containers according to a pattern

docker images -a | grep "pattern" | awk '{print $3}' | xargs docker rmi

answered Apr 26 '20 at 21:30

Elton Sandré

372
3
7

score 2 · Answer 26 · answered Oct 30 '21 at 11:31

The only thing that helped me here was

docker images | grep none | awk '{ print $3; }' | xargs docker rmi --force

I had 2 images . These were also relatively large at 160MB and I didn't want them.

I tried docker images prune, but it didn't help.

docker images | grep none | awk '{ print $3; }' | xargs docker rmi This command returned the following:

Error response from daemon: conflict: 0d1227b90e3a cannot be deleted (must be forced) - image is being used by stopped container c2c01a8c0cc9. Error response from daemon: Conflict: 791026064837 cannot be deleted (must be forced) - image used by stopped container 53dee16ceb19.

There were also still containers that needed these images.

With docker container ls -a | grep "c2c01a8c0cc9" I could check which dependency it was.

With:

docker images | grep none | awk '{ print $3; }' | xargs docker rmi --force

I have now deleted the images.

Since I no longer need this container, I deleted it with: docker container rm <container_name>

score 2 · Answer 27 · answered Jan 19 '22 at 09:37

2

With Docker Desktop for Windows you can get rid of the dangling images with

docker image prune

answered Jan 19 '22 at 09:37

Sergio Prats

1,043
1
14
19

score 1 · Answer 28 · answered May 24 '18 at 03:51

1

To remove dangling images please use :

docker image rm $(docker images --format "{{.ID}}" --filter "dangling=true")

Please refer to my answer here for a more detailed description : https://unix.stackexchange.com/a/445664/292327

answered May 24 '18 at 03:51

Aditya Satyavada

1,028
1
10
14

score 1 · Answer 29 · answered Dec 06 '18 at 06:48

1

The below command is working for me. this is just simple grep "" images and get the docker image id and removed all the images. Simple single command as it has to.

docker rmi $(docker images |grep "<none>"| awk '{print $3}')

answered Dec 06 '18 at 06:48

Jogendra Kumar

513
5
14

score 1 · Answer 30 · answered Jan 23 '19 at 21:50

This is an extension of tansadio's answer:

If you are getting following error:

Error response from daemon: conflict: unable to delete <> (must be forced) - image is being used by stopped container <>

You can force it with --force:

docker images | grep none | awk '{ print $3; }' | xargs docker rmi --force

score 1 · Answer 31 · answered May 14 '20 at 15:04

1

try this to see list docker images ID with tag <none>

docker images -a | awk '/^<none>/ {print $3}'

and then you can delete all image with tag <none>. this worked for me.

docker rmi $(docker images -a | awk '/^<none>/ {print $3}')

answered May 14 '20 at 15:04

nur zazin

1,018
13
13

score 1 · Answer 32 · answered Jul 07 '22 at 01:40

1

Pruning all images with force would solve your issue

docker image prune -a --force

answered Jul 07 '22 at 01:40

Mohammed Maaz

56
5

TheExorcist · Answer 33 · 2018-12-17T07:01:43.497

Its simple and clear,

Even I took 3 days to understand this simple and crisp error.

The docker image is not built successfully

Step 7/13 : COPY jupyter_notebook_config.py /root/.jupyter/
 ---> bf29ce6fe6dc
Step 8/13 : COPY notebooks /notebooks
COPY failed: stat /var/lib/docker/tmp/docker-builder776981166/notebooks: no such file or directory
anarchist@anarchist-desktop:~/Documents/sam/dockerDem$ docker images
REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
<none>              <none>              bf29ce6fe6dc        9 seconds ago       1.27GB
ubuntu              16.04               a51debf7e1eb        3 weeks ago         116MB

Then I removed the 8th line from Dockerfile, it was signal success this time.

Successfully built b6724370f8ca
Successfully tagged dem:expo
anarchist@anarchist-desktop:~/Documents/sam/dockerDem$ docker run -it -p 8888:8888 dem:expo
[I 06:11:38.984 NotebookApp] Writing notebook server cookie secret to /root/.local/share/jupyter/runtime/notebook_cookie_secret
[I 06:11:39.011 NotebookApp] Serving notebooks from local directory: /
[I 06:11:39.011 NotebookApp] The Jupyter Notebook is running at:
[I 06:11:39.011 NotebookApp] http://(296d81166725 or 127.0.0.1):8888/?token=496feb282ef749c05277ef57a51e8a56fedb1c6b337b9f92

It says successfully tagged dem:expo, this line is imp during docker process.

score 0 · Answer 34 · answered Feb 18 '19 at 02:43

0

docker rmi -f $(docker images -a|awk 'NR > 1 && $2 == "" {print $3}')

answered Feb 18 '19 at 02:43

iamfaith

1,097
1
7
2

score -2 · Answer 35 · answered Apr 02 '19 at 14:16

-2

The dangling images are ghosts from the previous builds and pulls, simply delete them with : docker rmi $(docker images -f "dangling=true" -q)

answered Apr 02 '19 at 14:16

Nathan Borik

31
3

The OP states that he did try this exact command already but it failed. Also, this answer has been given at least twice already. – CaringDev Apr 02 '19 at 14:43

user2915097 · Answer 36 · 2015-11-25T10:28:04.857

-4

try

docker rmi -f $(docker images -a | awk 'NR> 1 || $2 = "<none>" {print $3}') , while there may be cleaner commands

Updated

edited Nov 25 '15 at 10:28

answered Nov 25 '15 at 09:45

user2915097

30,758
6
57
59

4

That will *also* remove images which are not tagged which is a big nono. – basickarl Nov 25 '15 at 09:51
I have upated my answer – user2915097 Nov 25 '15 at 09:56
The command `docker rmi -f $(docker images -a | awk 'NR> 1 || $2 = "" {print $3}` does not do anything! – basickarl Nov 25 '15 at 09:58
I came across this a month back and it was all good because I read this comment and didn't use this command. I came back again, forgot to read this comment, and bam, all my images are gone. – Quark Apr 12 '23 at 19:30

score -8 · Answer 37 · answered Nov 25 '15 at 10:05

-8

docker rmi $(docker images -a -q)

Stated the following images where in use. I think this command gets rid of unwanted images.

answered Nov 25 '15 at 10:05

basickarl

37,187
64
214
335

3

doesn't this remove all images? – marianobianchi Jan 13 '17 at 14:19
4

this removes all unused images and it should not be marked as the correct answer. – Ghashange Mar 14 '17 at 17:01

Docker remove TAG images

37 Answers37

Diagnostic Steps

Linked

Related