Stephen J Day 4829e9685e registry/storage/driver: checking that non-existent path returns PathNotFoundError ... Issue #1186 describes a condition where a null tags response is returned when using the s3 driver. The issue seems to be related to a missing PathNotFoundError in s3. This change adds a test for that to get an idea of the lack of compliance across storage drivers. If the failures are manageable, we'll add this test condition and fix the s3 driver. Signed-off-by: Stephen J Day <stephen.day@docker.com>		2015-12-08 12:04:03 -08:00
..
api	Fix failing test case	2015-10-25 13:03:22 -04:00
auth	De-obfuscate error message	2015-11-06 17:10:28 -08:00
client	Merge pull request #1243 from RichardScothern/client-header-message	2015-12-08 09:54:18 -08:00
handlers	Map error type to error code	2015-12-01 22:26:37 +01:00
listener	[Server] Listen and serve on a unix socket	2015-05-11 16:00:14 +03:00
middleware	Add pull through cache functionality to the Registry which can be configured	2015-08-04 16:09:55 -07:00
proxy	Buffer writing the scheduler entry state to disk by periodically checking for	2015-10-29 11:35:52 -07:00
storage	registry/storage/driver: checking that non-existent path returns PathNotFoundError	2015-12-08 12:04:03 -08:00
doc.go	Move initialization code from main.go to the registry package	2015-09-09 14:39:31 -07:00
registry.go	Add WithVersion to context and other cleanup	2015-09-14 17:14:31 -07:00