distribution/registry
Yu Wang (UC) 2e94c22fe4 issue#2135 image pull returns 404 on manifest request if there is storage error
When get manifest, the handler will try to retrieve it from storage driver. When storage driver is cloud storage, it can fail due to various reasons even if the manifest exists
(like 500, 503, etc. from storage server). Currently manifest handler blindly return 404 which can be confusing to user.

This change will return 404 if the manifest blob doesn't exist, and return 500 UnknownError for all other errors (consistent with the behavior of other handlers).

Signed-off-by: Yu Wang (UC) <yuwa@microsoft.com>
2017-01-11 12:34:11 -08:00
..
api digest: migrate to opencontainers/go-digest 2017-01-06 15:42:03 -08:00
auth Add test for auth token with "*" action 2017-01-06 16:08:32 -08:00
client digest: migrate to opencontainers/go-digest 2017-01-06 15:42:03 -08:00
handlers issue#2135 image pull returns 404 on manifest request if there is storage error 2017-01-11 12:34:11 -08:00
listener [Server] Listen and serve on a unix socket 2015-05-11 16:00:14 +03:00
middleware Add support for blobAccessController middleware 2016-05-19 14:02:15 +02:00
proxy digest: migrate to opencontainers/go-digest 2017-01-06 15:42:03 -08:00
storage azure: revendor + remove hacky solution in is404 2017-01-09 17:22:28 -08:00
doc.go Move initialization code from main.go to the registry package 2015-09-09 14:39:31 -07:00
registry.go Update logrus vendor 2017-01-05 11:40:18 -08:00
registry_test.go Allow registry clients to connect via http2 2016-08-13 22:07:42 -04:00
root.go Remove signature store from registry. Return a generated signature for manifest 2016-05-27 13:19:26 -07:00