search

docker-archive / docker-registry

This is **DEPRECATED**! Please go to https://github.com/docker/distribution
Apache License 2.0
2.88k stars 879 forks source link

Image marked as _inprogress long after upload #875

Closed DGollings closed 9 years ago

DGollings commented 9 years ago

Docker client shows: 0f266faabe40: Error pulling image (1.6) from (..), HTTP code 400 ://(..)/v1/, HTTP code 400 2ab8ea4e97b4: Error pulling dependent layers 2015/01/02 13:57:47 Error pulling image (1.6) from (..), HTTP code 400

registry logs show: 02/Jan/2015:13:08:05 +0000 DEBUG: api_error: Image is being uploaded, retry later

Although the image (and those following it) have already been uploaded. Registry sits behind an nginx proxy but retagging and uploading directly to the private registry doesn't help. Updating registry to latest version (23 hours old), doesn't help Completely rebuilding image 'stack' - doesn't help, same error for a different image Simply waiting - doesn't help, three days after I initially noticed this the images was still _inprogress Different Docker versions and rebuilding stack - doesn't help (1.0, 1.3.1 and 1.3.3)

Finally figured it out: Images are marked as _inprogress, for seemingly no particular reason, fixed it by removing _inprogress find . -name '_inprogress' -exec rm {} \;

However, it would be nice to know why this happens in the first place

DGollings commented 9 years ago

Almost surely own fault:

Two way, but never delete, rsync script runs every minute, _inprogress is a file...