How to Delete Docker Containers, Images, and Volumes Safely

Docker cleanup has three separate targets: containers, images, and volumes. Removing a container does not automatically remove a named volume, and deleting a volume can permanently destroy application data.

Identify what you plan to remove

docker ps -a
docker image ls
docker volume ls

Record the exact name or ID before running a removal command.

Remove a stopped container

docker rm my-container

This removes the container object. It does not remove the image used to create it or a named volume attached to it.

To remove several stopped containers, review the list first:

docker container prune

Docker asks for confirmation and removes stopped containers only.

Remove an image

docker image rm nginx:1.27-alpine

Docker may refuse if a container still references the image. Remove or replace those containers first. Do not use --force until you understand which tags and image references will be affected.

Remove a volume

docker volume inspect my-data
docker volume rm my-data

Docker will not remove a volume that is still in use. Stop and remove the relevant containers first, then check the volume again.

Prune unused objects

docker image prune
docker container prune
docker volume prune

These commands target specific unused object types. Read the confirmation prompt carefully. docker system prune combines several cleanup operations, so it deserves extra caution.

Compose cleanup

docker compose down

This stops and removes the project’s containers and networks. It does not remove named volumes by default. Adding -v removes the Compose project’s named volumes too:

docker compose down -v

Safe cleanup checklist

1. List containers, images, and volumes.
2. Identify whether data is stored in a named volume or bind mount.
3. Back up important data.
4. Remove the container first.
5. Remove the image or volume only when you are certain it is unused.

Official references

See Docker’s container removal reference, volume documentation, and pruning guide.