b88539964d
This is a partial revert of I70a7bb5f73d1dddc540e96529784bb8c9bb0b9e3 The off-by-one error turned out to come from our range response (I1fb1abf3c76ea8db7820caa90c97ddbf92997842). There are no clients we know of that send an incorrect size in the manifest; we should error if we see that. Revert the adding of layer sizes done with Id5b1c5726fbe046b2f9f2994bf34f5fd7ecd90de and replace it with a hard error. I have tested both docker and podman pushes against this change and both correctly set a size for each layer in the manifest per [1]. Although I can not replicate it, the missing sizes might have already been fixed upstream, or related to the aforementioned off-by-one response we were giving. [1] https://docs.docker.com/registry/spec/manifest-v2-2/#manifest-list-field-descriptions Change-Id: Ibe061171bfd8ab6043b491bbab933bf277f8e12b |
||
---|---|---|
.. | ||
conf.yaml | ||
delete_container.py | ||
test.sh |