image is being used by stopped container

Question

I am trying to delete a docker container by this command:

docker rmi <Image-Id>

Obviously, I have replaced the Image-Id by the Id I get using:

docker images

But I see the error below:

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

score 156 · Accepted Answer · edited Jan 19 '21 at 02:11

156

You can also use --force , -f Force removal of the image

If you use the -f flag and specify the image’s short or long ID, then this command untags and removes all images that match the specified ID.

  docker rmi -f <image_id>

Note: this command removes images being used by containers.

edited Jan 19 '21 at 02:11

Giovani

95
6

answered Jul 05 '18 at 10:58

Adiii

35,809
6
84
87

1

Thanks, It worked fine but there is an issue. I deleted a 10 GB image but after deleting it, I cannot see any change in my free disk space. – Mehrdad Babaki Jul 06 '18 at 09:36
1

did you remove volumes attach with image and did you check image size of each – Adiii Jul 06 '18 at 09:48
1

Not really, I am new to docker. I will try the tool.By the way can I use command line to detect volume and remove them? – Mehrdad Babaki Jul 06 '18 at 11:22
1

yes docker volume ls ; to list volume and to remove, docker volume rm v_id – Adiii Jul 07 '18 at 00:23

score 45 · Answer 2 · answered Jul 05 '18 at 10:55

45

You need to delete the stopped container with docker rm, and then you can delete the image it uses with docker rmi.

answered Jul 05 '18 at 10:55

David Maze

67,477
12
66
91

3

This is part of any complete answer. You can either force removal or delete the stopped image. – bmacnaughton Nov 07 '18 at 17:47

Angus · Answer 3 · 2019-06-05T20:46:16.433

38

You may also find that you have stopped containers that are causing the lock. Remove these first using:

docker rm  $(docker ps -q -a)

Here we are listing the docker processes by just the ID and then removing those; however, docker rm will only remove stopped containers.

Next go back and remove the images using:

docker image rm <image_id>

edited Jun 05 '19 at 20:46

answered Jun 05 '19 at 19:39

Angus

381
3
5

score 28 · Answer 4 · answered Feb 04 '20 at 10:01

28

You must remove container first.
Forced is the last method to take.

#check container
docker ps -a

#remove container
docker rm containerID

answered Feb 04 '20 at 10:01

Hideyasu.T

467
4
3

4

Clearly the best answer. The only one who explain how to get the list of stopped container. – Marco May 27 '20 at 20:00

score 5 · Answer 5 · answered Jun 07 '20 at 22:04

5

In case docker rmi <image-id> didn't work, try this:

Stop all running containers

docker stop $(docker ps -aq)

Remove all containers

docker rm $(docker ps -aq)

Remove all images

docker rmi $(docker images -q)

answered Jun 07 '20 at 22:04

arilwan

1,952
2
16
29

score 5 · Answer 6 · answered Jun 13 '20 at 17:39

If the goal is to reclaim disk space, another approach not yet mentioned is to use docker system prune. It will print a warning which should be heeded:

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

This will not delete named images, but will purge intermediate unnamed images. Depending on the sizes of containers you're using, this can save a considerable amount of disk space.

score 3 · Answer 7 · answered May 09 '20 at 20:07

In addition to the other answers, I had the same issue using Docker for Mac but docker ps -a did not show any running containers. Running docker images shows:

docker/desktop-storage-provisioner   v1.0                605a0f683b7b        2 months ago        33.1MB
k8s.gcr.io/kube-controller-manager   v1.15.5             1399a72fa1a9        6 months ago        159MB
k8s.gcr.io/kube-proxy                v1.15.5             cbd7f21fec99        6 months ago        82.4MB
k8s.gcr.io/kube-apiserver            v1.15.5             e534b1952a0d        6 months ago        207MB
k8s.gcr.io/kube-scheduler            v1.15.5             fab2dded59dd        6 months ago        81.1MB
docker/kube-compose-controller       v0.4.23             a8c3d87a58e7        11 months ago       35.3MB
docker/kube-compose-api-server       v0.4.23             f3591b2cb223        11 months ago       49.9MB
k8s.gcr.io/coredns                   1.3.1               eb516548c180        16 months ago       40.3MB
k8s.gcr.io/etcd                      3.3.10              2c4adeb21b4f        17 months ago       258MB
k8s.gcr.io/pause                     3.1                 da86e6ba6ca1        2 years ago         742kB

All of these images are used by the Docker app if you have Kubernetes enabled. In the Docker for Mac preferences, there is a section for Kubernetes. If you click "Show system containers (advanced)", they will appear in docker ps.

If you wish to delete these images, you need to disable Kubernetes via the Docker for Mac app, then try again.

score 2 · Answer 8 · answered Oct 07 '19 at 13:11

2

Docker containers run on top of docker images, you can delete an image only if it is not attached to any container.! So you have to stop container and remove container then you can remove image id.

docker stop container-id and docker rm container-id

Then try removing image docker rmi image-id

Some extra info given in below link. Cheers.!

https://docs.docker.com/config/pruning/

answered Oct 07 '19 at 13:11

surya kiran

329
3
10

This should be the correct answer following the process of stop container (docker-compose stop )-> remove container (docker rm )-> remove associated images (docker rmi ). – kta Mar 16 '20 at 01:57

ans1genie · Answer 9 · 2019-04-04T13:32:42.463

0

If you have changed in the Dockerfile and if you are using docker compose, you can just rebuild your image by run docker-compose with the --build option !

edited Apr 04 '19 at 13:32

answered Apr 04 '19 at 11:27

ans1genie

329
1
4
12

If you made any changes on the `Dockerfile` you shoudn't remove the image yourself just use the flag `--build` with `docker-compose` so it rebuild a new image with the changes – ans1genie Apr 04 '19 at 13:37

image is being used by stopped container

9 Answers9

Linked