Your Docker host is running out of disk space. Again.
Old images pile up fast, especially after multiple builds and deployments. Learning how to remove Docker images keeps your system clean and your storage under control.
Unused container images consume gigabytes without serving any purpose. Dangling layers from failed builds make it worse.
This guide covers every deletion method: single images, batch removal, force deletion, and automated pruning with filters.
You’ll learn the exact Docker CLI commands for each scenario, plus troubleshooting steps for common errors.
Takes about 5-10 minutes. Works on Linux, macOS, and Windows.
How to Remove Docker Images
Removing Docker images is the process of deleting container images from your local storage to free up disk space and clean your development environment.
You need this when dangling images pile up after builds, when old versions clutter your system, or when you want to reclaim storage on your machine.
This guide covers 8 methods requiring 5-10 minutes and basic Docker command line knowledge.
Prerequisites
Before running any cleanup commands, make sure you have the following ready:
- Docker Engine version 20.10 or later installed
- Terminal access (Bash, PowerShell, or Command Prompt)
- Admin or sudo permissions on your system
- 5-10 minutes depending on image count
Not sure if Docker is running? Check your Docker daemon status first.
If you haven’t set up Docker yet, follow the steps to install Docker on your operating system.
Step 1: How Do You List All Docker Images on Your System?
Run docker images or docker image ls in your terminal to display all local images with their repository names, tags, image IDs, creation dates, and sizes.
Command:
“ docker images `
Expected output:
` REPOSITORY TAG IMAGE ID CREATED SIZE nginx latest a6bd71f48f68 2 days ago 187MB python 3.11 f5f1a1a1a1a1 5 days ago 1.01GB node 18 b2b2b2b2b2b2 1 week ago 998MB `
Add the -a flag to include intermediate image layers created during builds.
Why This Step Matters
You need the image ID or repository:tag combination to target specific images for deletion.
Skipping this step means guessing which images exist on your system.
Step 2: How Do You Remove a Single Docker Image by ID or Name?
Use docker rmi [IMAGEID] or docker rmi [REPOSITORY:TAG] to delete one image from local storage.
Command with Image ID:
` docker rmi a6bd71f48f68 `
Command with Repository and Tag:
` docker rmi nginx:latest `
The terminal outputs Untagged: and Deleted: messages confirming each removed layer.
Why This Step Matters
Single image removal gives precise control over what stays and what goes.
Use this for targeted cleanup without affecting other images in your containerization workflow.
Step 3: How Do You Force Remove a Docker Image That Is In Use?
Add the -f flag to forcefully delete an image even when a container references it: docker rmi -f [IMAGEID].
Command:
` docker rmi -f a6bd71f48f68 `
This removes the image regardless of existing container dependencies.
When to Use Force Removal
- Stopped containers still reference the image
- You get “image is being used” errors
- Quick cleanup during development (not production)
Why This Step Matters
Sometimes Docker refuses deletion because a stopped container depends on that image.
The force flag bypasses this check. Use carefully in production environments.
Step 4: How Do You Remove Multiple Docker Images at Once?
Pass multiple image IDs or names to docker rmi separated by spaces: docker rmi image1 image2 image3.
Command:
` docker rmi nginx:latest python:3.11 node:18 `
Or remove images matching a pattern using command substitution:
` docker rmi $(docker images -q nginx) `
This deletes all nginx images regardless of tag.
Why This Step Matters
Batch deletion saves time when cleaning multiple outdated images from your build pipeline.
Step 5: How Do You Remove All Unused Docker Images?
Run docker image prune to delete all dangling images not associated with any container.
Command:
` docker image prune `
Docker prompts for confirmation. Add -f to skip the prompt.
` docker image prune -f `
Output shows total reclaimed space in MB or GB.
Why This Step Matters
Dangling images accumulate after failed builds and consume significant disk space without serving any purpose.
Step 6: How Do You Remove All Docker Images Including Tagged Ones?
Add the -a flag to prune: docker image prune -a removes all images not used by existing containers.
Command:
` docker image prune -a `
This includes tagged images. You’ll need to pull them again from Docker Hub or your container registry.
When to Use Complete Pruning
- Starting fresh on a development machine
- Clearing space before a major project
- Resetting your local Docker environment
Why This Step Matters
Complete image removal reclaims maximum disk space but requires re-downloading needed images.
Step 7: How Do You Remove Docker Images by Filter or Pattern?
Use the –filter flag with prune to target images by age or label.
Remove images older than 24 hours:
` docker image prune -a --filter "until=24h" `
Remove images older than 7 days:
` docker image prune -a --filter "until=168h" `
Remove by label:
` docker image prune --filter "label=environment=dev" `
Why This Step Matters
Filtered cleanup integrates well with continuous integration scripts and automated maintenance in DevOps workflows.
Step 8: How Do You Remove Dangling Docker Images?
Dangling images show for repository and tag. They're leftover layers from builds.
List dangling images:
` docker images -f "dangling=true" `
Remove all dangling images:
` docker image prune `
Or target them directly:
` docker rmi $(docker images -f "dangling=true" -q) `
Why This Step Matters
Dangling images represent wasted storage; removing them is the safest cleanup method since no container uses them.
Verification
Confirm successful removal with these commands.
Check remaining images:
` docker images `
View disk usage:
` docker system df `
Output shows Images, Containers, and Volumes with total size, active usage, and reclaimable space.
` TYPE TOTAL ACTIVE SIZE RECLAIMABLE Images 3 2 1.2GB 450MB (37%) Containers 2 1 50MB 25MB (50%) Volumes 5 3 500MB 200MB (40%) `
Troubleshooting
Issue: Image Is Being Used by a Stopped Container
Error: conflict: unable to remove repository reference… container is using its referenced image
Solution: Remove the dependent container first, then the image.
` docker rm [CONTAINERID] docker rmi [IMAGEID] `
Or list containers using that image: docker ps -a –filter ancestor=[IMAGEID]
Learn more about stopping containers before removal.
Issue: Permission Denied Error
Error: permission denied while trying to connect to the Docker daemon socket
Solution on Linux:
` sudo docker rmi [IMAGEID] `
Or add your user to the docker group:
` sudo usermod -aG docker $USER `
Log out and back in for changes to apply.
Issue: Image Has Dependent Child Images
Error: image has dependent child images
Solution: Find and remove child images first.
` docker image inspect --format='{{.RepoTags}} {{.Id}} {{.Parent}}' $(docker images -q) `
Delete children before parents, or use force removal with docker rmi -f.
Related Processes
Docker image management connects to other cleanup and maintenance tasks.
- Creating Docker containers from your remaining images
- Docker volume storage locations for volume cleanup
- Docker Compose for multi-container image management
- Docker image storage paths for manual cleanup
For complete system cleanup including containers, networks, and volumes:
` docker system prune -a --volumes `
This command removes everything unused. Run with caution in shared environments.
FAQ on How To Remove Docker Images
What is the difference between docker rmi and docker image prune?
The docker rmi command removes specific images by ID or name. The docker image prune command deletes all dangling images automatically.
Use rmi for targeted removal. Use prune for bulk cleanup of unused images.
Can I recover a deleted Docker image?
No. Once removed, Docker images cannot be recovered from local storage.
You must pull the image again from Docker Hub or your private registry. Always verify before running delete commands.
Why does Docker say “image is being used by a container”?
A container (running or stopped) depends on that image. Docker prevents deletion to avoid breaking container references.
Remove the dependent container first with docker rm, or use docker rmi -f to force deletion.
How do I remove all Docker images at once?
Run docker rmi $(docker images -q) to delete every image on your system.
This removes all images regardless of status. Your codebase remains unaffected since images are separate from source files.
What are dangling Docker images?
Dangling images show for repository and tag. They're orphaned layers from builds where newer versions replaced them.
Remove them with docker image prune to reclaim disk space safely.
Does removing Docker images affect running containers?
Docker blocks deletion of images used by running containers. You’ll get an error message.
Stop the container first using docker stop, then remove the image. Running containers always have protection.
How much disk space do Docker images use?
Run docker system df to check. Images typically consume 100MB to several GB each depending on the base image and layers.
Alpine-based images use less space than Ubuntu or Debian variants.
Can I remove Docker images from a specific date range?
Yes. Use the filter flag: docker image prune -a –filter “until=72h” removes images older than 72 hours.
This works well in continuous deployment pipelines for automated cleanup.
What happens to image layers when I delete an image?
Docker removes layers not shared with other images. Shared layers stay until all dependent images are deleted.
This layered architecture optimizes storage by avoiding duplicate data.
How do I delete Docker images in Docker Desktop?
Open Docker Desktop, click Images in the sidebar, hover over the target image, and click the trash icon.
Command line methods work identically in Docker Desktop’s integrated terminal.
Conclusion
Knowing how to remove Docker images keeps your development environment efficient and your storage under control.
You now have every method: single image deletion with docker rmi, batch removal, force deletion, and automated pruning with date filters.
The docker system df` command shows exactly how much space you can reclaim. Run it regularly.
For ongoing container cleanup, integrate pruning commands into your build automation tools or scheduled maintenance scripts.
Start with dangling images. They’re safe to remove and often consume gigabytes.
Then move to unused tagged images when you need more space.
Regular image management prevents the storage problems that slow down builds and deployments on your Docker Engine host.
Many of his resources are available on various design marketplaces and for free on Codepen.
Over the years, he's worked with a range of clients and contributed to design publications like Design Your Way, Designmodo, WebDesignerDepot, WPDean, Speckyboy, and Slider Revolution among others.
