conflict: unable to delete image (cannot be forced) - image has dependent child images
Other images were built on top of this one, so Docker won’t delete it by ID.
image has dependent child imagesunable to delete(cannot be forced) Meaning
Images share layers. If you built myapp FROM a local base image, the base can’t be removed while myapp exists. Delete the children first, or remove by tag instead of by ID.
Common causes
- Other local images use this image as a parent layer
- Deleting by image ID when several tags point to it
⚡ Quick fix
- Find children: docker image ls --filter since=<id>
- Remove child images first
- Use docker image prune -a to remove all unused images
Detailed fix by platform
Docker
- bash
docker image ls --filter since=9b1e0c1d2e3f docker image prune -a
How to diagnose
- Children — Images created after it that use it
- Tags — docker images | grep <id>
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Docker
- docker-credential-desktop error getting credentials - err: exec: "docker-credential-desktop": executable file not found in $PATH
- pull access denied pull access denied for image, repository does not exist or may require 'docker login'
- lookup registry-1.docker.io: no such host dial tcp: lookup registry-1.docker.io: no such host / Temporary failure in name resolution during docker build
Other ways to find it
Where this error sits
Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 13 Oct 2026