Remove Docker images without confusing tags and data

Use docker image rm (also called docker rmi) to remove a local image reference. Inspect the active Docker context and the affected containers first; a remote context means these commands operate on that remote daemon.

docker context show
docker image ls -a
docker image rm myapp:old
docker image rm myapp:test worker:test

An image ID is also accepted. A tag is a reference: removing one tag may leave the same image accessible through other tags, while unreferenced content can be reclaimed when no remaining dependency requires it.

Resolve container conflicts deliberately

List containers associated with the image before deciding whether to remove them:

docker container ls -a --filter ancestor=myapp:old

This filter can include descendants of the image, so review its results. If a specific stopped container is no longer needed and its writable data has been preserved, remove that container by name and retry:

docker container rm old-app
docker image rm myapp:old

Force removal can resolve certain reference conflicts, but it is not a universal bypass for all image dependencies. It does not update running containers to another image or delete the remote registry copy.

Prune unused images

docker image prune
docker image prune -a

The default targets eligible dangling images. -a also targets tagged images unused by containers. Read the confirmation and retain rollback images where needed.

docker system prune -a has broader scope: it can also remove stopped containers, unused networks and build cache. It is not equivalent to deleting all running containers and images; it retains resources still in use.

If you intend a complete local reset

The following Bash example forcibly removes every container visible to the selected daemon, including running ones, and then attempts to remove every image. It discards container writable layers. Use it only after reviewing that exact scope and preserving necessary data:

set -euo pipefail
container_ids=$(docker container ls -aq)
if [ -n "$container_ids" ]; then
  docker container rm -f $container_ids
fi
image_ids=$(docker image ls -aq | sort -u)
if [ -n "$image_ids" ]; then
  docker image rm -f $image_ids
fi

Empty-list guards avoid invoking removal with no targets. This example omits volume-deletion flags; volumes require a separate, deliberate retention decision. Some image dependencies may still need investigation.

FAQ

Why was little disk space released? Layers can be shared, and deleting a tag may only remove a reference. Inspect docker system df -v; builder cache and Docker Desktop's disk allocation are separate considerations.

How do I delete a registry image? Use the registry's deletion and retention features. Local rmi does not delete remote artifacts; registry garbage collection follows that registry's own rules.

Can Docker keep only the newest N releases? Image removal has no general “keep newest N releases” policy. Use an explicit retention process that understands tags, digests, active deployments and rollback requirements, or the registry's retention controls.

See Removing local images, Pruning unused images, System prune scope.