Home>Article>Operation and Maintenance> What should I do if docker cannot delete the image?

What should I do if docker cannot delete the image?

藏色散人
藏色散人 Original
2022-01-20 15:25:32 5515browse

Solution to the problem that docker cannot delete the image: 1. Delete REPOSITORY; 2. Delete IMAGE ID; 3. View the image through "docker images".

What should I do if docker cannot delete the image?

The operating environment of this article: centOS6.8 system, Docker version 18.09.x, Dell G3 computer.

What should I do if docker cannot delete the image?

How to solve the problem that the Docker Image cannot be deleted

Foreword

##Docker It is an open source container engine project based on lightweight virtualization technology by Docker.Inc. The entire project is developed based on Go language and complies with the Apache 2.0 protocol. Through layered image standardization and kernel virtualization technology, Docker enables application developers and operation and maintenance engineers to publish applications across platforms in a unified manner, and provides a resource-isolated application running environment with almost no additional overhead. Due to its many novel features and the openness of the project itself, Docker has quickly gained participation from many IT vendors in less than two years, including industry leaders such as Google, Microsoft, and VMware. At the same time, Docker has also stirred up waves in the developer community. Many coders like me have begun to pay attention to, learn and use Docker. Many companies, especially Internet companies, are also increasing their investment in Docker. Set off a container revolution.

Found the problem:

Image is one of the core technologies of Docker and is also the standard format for application release. Recently encountered a problem at work, the problem is as follows:

Error response from daemon: conflict: unable to delete 4ac2d12f10cd (must be forced) - image is referenced in multiple repositories

Error response from daemon: Conflict: cannot remove 4ac2d12f10cd (must be forced) - Image is referenced in multiple repositories


1. Delete the image

View the image

root@souyunku:~/mydocker# docker images REPOSITORY TAG IMAGE ID CREATED SIZE nginx v1 4ac2d12f10cd 41 minutes ago 108MB souyunku/nginx v1 4ac2d12f10cd 41 minutes ago 108MB hello-world latest f2a91732366c 5 weeks ago 1.85kB

Delete failed

Delete one of the images, the image here has 1 repo reference, and no container uses it

And no container uses it

root@souyunku:~/mydocker# docker container ls -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 4c104074b3f4 hello-world "/hello" About an hour ago Exited (0) About an hour ago priceless_hawking

The image has 1 repo reference

root@souyunku:~/mydocker# docker rmi 4ac Error response from daemon: conflict: unable to delete 4ac2d12f10cd (must be forced) - image is referenced in multiple repositories

2. Solution

Delete REPOSITORY

Deleted ImageID, there is 1 REPOSITORY name here Quote, the solution is as follows:

Specify the name when deleting, not the IMAGE ID.

root@souyunku:~/mydocker# docker rmi souyunku/nginx:v1 Untagged: souyunku/nginx:v1

Just delete the IMAGE ID:

root@souyunku:~/mydocker# docker rmi 4ac Untagged: nginx:v1 Deleted: sha256:4ac2d12f10cdb99c099749432b7a450ee1c6958e0f2f964cd64c6b086ba3e622 Deleted: sha256:346164f732e08d72d1f64828acda4e5ca93f79473f443ce57d9cfe69d9b66b24 Deleted: sha256:3f8a4339aadda5897b744682f5f774dc69991a81af8d715d37a616bb4c99edf5 Deleted: sha256:bb528503f6f01b70cd8de94372e1e3196fad3b28da2f69b105e95934263b0487 Deleted: sha256:410204d28a96d436e31842a740ad0c827f845d22e06f3b1ff19c3b22706c3ed4 Deleted: sha256:2ec5c0a4cb57c0af7c16ceda0b0a87a54f01f027ed33836a5669ca266cafe97a

3. View the mirror

root@souyunku:~/mydocker# docker images REPOSITORY TAG IMAGE ID CREATED SIZE hello-world latest f2a91732366c 5 weeks ago 1.85kB

Recommended study:《

docker video tutorial

The above is the detailed content of What should I do if docker cannot delete the image?. For more information, please follow other related articles on the PHP Chinese website!

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn