docker registry ai_generated true

layer already being pulled by another client. Waiting...

ID: docker/layer-already-being-pulled

Also available as: JSON · Markdown
92%Fix Rate
93%Confidence
50Evidence
2023-01-01First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
24 active — — —

Root Cause

Another Docker pull is downloading the same layer concurrently.

generic

Workarounds

  1. 90% success Wait for the other pull to complete — this is expected behavior during parallel pulls 
    Docker daemon serializes layer downloads; the second pull reuses the first's result
  2. 85% success If stuck, restart Docker daemon: sudo systemctl restart docker 
    Clears stuck layer downloads; running containers will stop

Dead Ends

Common approaches that don't work:

  1. Canceling and restarting the pull 60% fail

    Will hit the same issue if another pull is still running

  2. Deleting all local images to force a fresh pull 75% fail

    Wastes bandwidth; all images need to be re-downloaded

Error Chain

Frequently confused with: