Size column in Tags list view always 0 about docker-registry-web HOT 4 CLOSED

Can you check if problem fixed in latest version?

from docker-registry-web.

My Java (and especially Groovy) is really weak, but, the tags list view determines the blob size(s) with:

restService.headLength("${name}/blobs/${digest}") ?: 0

the image details view uses:

entry.Size ?: restService.headLength("${name}/blobs/${blobs[i]}")
(entry being an entry of the list of history.v1Compatibility)

Meaning that if the headLength call fails for whatever reason; one returns 0, but the other uses the Size field from the history.v1Compatibility json strings. I have a feeling it would be prudent to make both use the same method, either fixing a possible problem in a comparable fashion in one or for forcing a possible bug in the other.

from docker-registry-web.

Thank for bug report, @madeddie.
The problem is entry.Size used only for compatibility with images created in docker engine version < 1.10. It seems working in you case but should no longer work with freshly generated images.
What registry storage backend are you using?

from docker-registry-web.

Yes, the sizes are there now. The loading of the tags list is somewhat slower, so I assume it actually does something it didn't do before :)

We're using the s3 backend.
We host quite some older images from around docker engine 1.6, so that would explain why the v1comp stuff still worked :)

from docker-registry-web.