image has dependent child images Docker Origin: Platform & cloud OSI layer 7 · Application Last updated 13 Oct 2026

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.

Exact message you may see image has dependent child imagesunable to delete(cannot be forced)
Seen on: Docker

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

  1. Find children: docker image ls --filter since=<id>
  2. Remove child images first
  3. Use docker image prune -a to remove all unused images

Detailed fix by platform

Docker

  1. bash
    docker image ls --filter since=9b1e0c1d2e3f
    docker image prune -a

How to diagnose

  1. Children — Images created after it that use it
  2. 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:

Where this error sits

Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):

1011 — Cloudflare Error 1011: Access denied (Hotlinking denied) (Cloudflare)1011conflict: unable to remove repository reference — conflict: unable to remove repository reference (must force) - container is using its referenced image (Docker)conflict: unable to r…ENOSPC — no space left on device (Docker / Linux) (Docker)ENOSPCexec format error — exec /usr/local/bin/docker-entrypoint.sh: exec format error (Docker)exec format errorGD missing — Fatal error: Uncaught Error: Call to undefined function imagecreatefromjpeg() (PHP)GD missinginvalid reference format — docker: invalid reference format (repository name must be lowercase) (Docker)invalid reference for…manifest unknown — manifest for image:tag not found: manifest unknown (Docker)manifest unknownmax depth exceeded — Error response from daemon: max depth exceeded (too many image layers) (Docker)max depth exceededimage has…

Explore the map of this error Full error map →

🧠 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.