{"id":3574,"date":"2023-11-17T17:12:11","date_gmt":"2023-11-17T09:12:11","guid":{"rendered":"https:\/\/www.servergigabit.com\/guide\/?post_type=kb&p=3574"},"modified":"2026-03-17T11:14:55","modified_gmt":"2026-03-17T03:14:55","slug":"removing-unused-docker","status":"publish","type":"kb","link":"https:\/\/www.servergigabit.com\/guide\/kb\/removing-unused-docker","title":{"rendered":"Removing Unused Docker Images, Containers, and Volumes: A Complete Guide"},"content":{"rendered":"
\n
\"Removing<\/div>\n<\/header>\n
\n

Docker<\/a> is a popular tool for managing containerized applications. However, over time, unused Docker images, volumes, and containers can accumulate on your system, consuming valuable disk space. This guide provides a comprehensive overview of the various commands and techniques for removing unused Docker elements, ensuring an efficient and organized Docker environment.<\/p>\n

Removing unused Images, Containers, Volumes and Networks<\/strong><\/h2>\n

The docker system prune<\/code> command effectively removes dangling and untagged resources, including images, containers, volumes, and networks. For a more comprehensive cleanup, including unused images and stopped containers, use the -a<\/code> flag:<\/p>\n

\n
docker system prune -a<\/code><\/pre>\n<\/div>\n
Removing Volumes<\/strong><\/h2>\n
Removing Specific<\/em> Docker Volumes<\/strong><\/h3>\n
o remove specific Docker volumes, use the docker volume ls<\/code> command to identify the volume names. Subsequently, employ the docker volume rm<\/code> command, specifying the desired volume names:<\/p>\n
\n
docker volume ls\r\ndocker volume rm [volume_name]<\/code><\/pre>\n<\/div>\n
Removing Dangling<\/em> Docker Volumes<\/strong><\/h3>\n
For dangling volumes, which persist even after the associated container is deleted, use the docker volume ls<\/code> command with the -f dangling=true<\/code> filter to identify them. Then, execute the docker volume prune<\/code> command to eliminate all dangling volumes:<\/p>\n
\n
docker volume ls -f dangling=true<\/span>\r\ndocker volume prune<\/code><\/pre>\n<\/div>\n
Removing Containers and Associated<\/em> Volumes\u00a0<\/strong><\/h3>\n
To simultaneously remove a container and its associated unnamed volume, use the -v<\/code> flag with the docker rm<\/code> command:<\/p>\n
\n
docker rm -v [container_name]<\/code><\/pre>\n<\/div>\n
Removing Docker Images<\/strong><\/h2>\n
Removing Specific<\/em> Docker Images<\/strong><\/h3>\n
To identify image IDs for deletion, use the docker images -a<\/code> command, which displays all images, including intermediate layers. Then, use the docker rmi<\/code> command with the desired image IDs or tags:<\/p>\n
\n
docker images -a\r\ndocker rmi [Image]<\/code><\/pre>\n<\/div>\n
Depending on the number of images on your server, the output will look something like this:<\/p>\n
\"How<\/picture><\/figure>\n
Remove Dangling<\/em> Images<\/strong><\/h3>\n
For dangling images, which are detached from any tagged images, use the docker images -f dangling=true<\/code> command to identify them. Subsequently, execute the docker image prune<\/code> command to remove them:<\/p>\n
\n
docker images -f dangling=true<\/span>\r\ndocker [Image] prune<\/code><\/pre>\n<\/div>\n
Here\u2019s an example for the output:<\/p>\n
\"How<\/picture><\/figure>\n
Remove Images Based on a Particular Pattern<\/em><\/strong><\/h3>\n
To remove images based on a specific pattern, combine the docker images<\/code> command with grep<\/code> to locate matching images. Then, use awk<\/code> and xargs<\/code> to pass their IDs to the docker rmi<\/code> command:<\/p>\n
\n
docker images -a | grep \"pattern\"<\/span> | awk '{print $3}'<\/span> | xargs docker rmi<\/code><\/pre>\n<\/div>\n
Remove All<\/em> Images\u00a0<\/strong><\/h3>\n
Finally, to remove all images, use the docker images -a<\/code> command to display all Docker images on your system. Then, add the -q<\/code> flag to pass the image IDs to the docker rmi<\/code> command:<\/p>\n
\n
docker rmi $(docker images -a -q)<\/code><\/pre>\n<\/div>\n
Removing Containers<\/strong><\/h2>\n
Removing Specific<\/em> Containers\u00a0<\/strong><\/h3>\n
To identify containers for removal, use the docker ps -a<\/code> command, which displays all containers, including those that are stopped or exited. Then, use the docker rm<\/code> command with the container IDs or names:<\/p>\n
\n
docker ps -a\r\ndocker rm [CONTAINER-ID-OR-NAME]<\/code><\/pre>\n<\/div>\n
Remove a Container Automatically<\/em> When It Exits\u00a0<\/strong><\/h3>\n
To automatically remove a container upon its exit, include the --rm<\/code> flag with the docker run<\/code> command:<\/p>\n
\n
docker run --rm image_name<\/code><\/pre>\n<\/div>\n
Removing Exited<\/em> Containers<\/strong><\/h3>\n
To remove only exited containers, use the -f status=exited<\/code> filter with the docker ps<\/code> command to identify them. Then, use the -q<\/code> flag to pass their IDs to the docker rm<\/code> command:<\/p>\n
\n
docker ps -a -f status=exited\r\ndocker rm $(docker ps -a -f status=exited -q)<\/code><\/pre>\n<\/div>\n
Removing Containers Using Filters<\/em><\/strong><\/h3>\n
To combine Docker filters, repeat the -f<\/code> flag and add additional values. For instance, to remove containers based on name or exited status, use:<\/p>\n
\n
docker ps -a -f status=exited -f name=[Name]\r\ndocker rm $(docker ps -a -f status=exited -f name=[Name] -q)<\/code><\/pre>\n<\/div>\n
Remove Containers Based on a Particular Pattern<\/em><\/strong><\/h3>\n
To remove containers matching a specific pattern, combine docker ps<\/code> with grep<\/code> to identify them. Then, use awk<\/code> and xargs<\/code> to pass their IDs to docker rm<\/code>:<\/p>\n
\n
docker ps -a | grep \"pattern\"<\/span> | awk '{print $1}'<\/span> | xargs docker rm<\/code><\/pre>\n<\/div>\n
Stop and Remove all Containers\u00a0<\/strong><\/h3>\n
To stop and remove all containers, use the docker ps -a<\/code> command to view all containers, including those that are not running. Then, use the -q<\/code> flag to pass their IDs to the docker stop<\/code> and docker rm<\/code> commands:<\/p>\n
\n
docker stop $(docker ps -a -q)\r\ndocker rm $(docker ps -a<\/code><\/pre>\n<\/div>\n
Conclusion<\/strong><\/h2>\n
In conclusion, this guide has provided comprehensive instructions for effectively managing Docker resources, including removing unnecessary images, containers, and volumes. By implementing these techniques, you can optimize your Docker environment,<\/span> ensuring efficient disk usage and a well-organized system.<\/span> Remember to save this guide as a cheat sheet for future reference!<\/span><\/p>\n<\/div>\n
If you need to know additional information such as how to install Docker on Ubuntu, you can refer this article<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
Docker is a popular tool for managing containerized applications. However, over time, unused Docker images, volumes, and containers can accumulate on your system, consuming valuable disk space. This guide provides a comprehensive overview of the various commands and techniques for removing unused Docker elements, ensuring an efficient and organized Docker environment. Removing unused Images, Containers, Volumes and Networks The docker…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"kbtopic":[1099],"kbtag":[1152,1218,1217,1219],"class_list":["post-3574","kb","type-kb","status-publish","hentry","kbtopic-tutorials","kbtag-containers","kbtag-image","kbtag-removing-unused","kbtag-volumes"],"_links":{"self":[{"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/kb\/3574","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/kb"}],"about":[{"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/types\/kb"}],"author":[{"embeddable":true,"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/comments?post=3574"}],"version-history":[{"count":6,"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/kb\/3574\/revisions"}],"predecessor-version":[{"id":6350,"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/kb\/3574\/revisions\/6350"}],"wp:attachment":[{"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/media?parent=3574"}],"wp:term":[{"taxonomy":"kbtopic","embeddable":true,"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/kbtopic?post=3574"},{"taxonomy":"kbtag","embeddable":true,"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/kbtag?post=3574"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}