Using S3 storage for Registry will not work, if the bucket is empty for ~30s
Summary
Creating a registry store on S3 will eventually lead it to become unaccessible due to health checks.
See #3011 (closed)
Steps to reproduce
- Follow guide here to set up S3
- Observe that the registry service will return 503's
- #3011 (closed) contains some logs that points to the healthchecks failing on empty buckets
What is the current bug behavior?
It seems a healthcheck is reacting to a set of 0 files returned from S3, rather than reacting to an error (unable to list files f.ex.).
What is the expected correct behavior?
If the bucket exists and responds 200 OK on listing, it should not be considered as failed.
Relevant logs
N/A
Details of package version
11.2.3-ce.0
Environment details
- Operating System:
Ubuntu 16.04
- Installation Target, remove incorrect values:
- AWS
- Installation Type, remove incorrect values:
- Other:
Migration from filesystem driver to S3 driver
- Other:
- Is there any other software running on the machine:
- Is this a single or multiple node installation? Single
- Resources
- CPU:
- Memory total: