Docker Registry 2.0, data stored in S3.
SSL is not enabled; the intent is that a reverse proxy will be used (such as
provide both connection security and authentication/authorization.
This Docker Registry build was made by starting with these instructions:
Building Production docker-registry
All secrets are passed in at run time, via environmental variables.
Note that this image exposes and has the registry listening on port 5000.
All configuration is accomplished by overriding runtime stanzas in the docker registry configuration file, as specified in the docs:
Overriding Configuration Options
In particular, the environmental variables which must be set are: (inoperative values given)
REGISTRY_HTTP_SECRET=replace-this-secret-with-long-alphanumeric REGISTRY_STORAGE_S3_ACCESSKEY=YKGMQJUH4A5JSDKR0PCFH REGISTRY_STORAGE_S3_SECRETKEY=CPZOTKPUIFMTDS3P39X6EKAXF0TIR9PAF14HWSZBT1J9V REGISTRY_STORAGE_S3_REGION=us-east-1 REGISTRY_STORAGE_S3_BUCKET=my_special_bucket