Multiple storage drivers panic in private registry

Question

I'm trying to deploy an S3-backed private docker registry and I'm getting an error when I try to start the registry container. My docker-compose.yml looks like this:

registry:
  restart: always
  image: registry:2
  ports:
    - 5000:5000
  environment:
    REGISTRY_STORAGE_S3_ACCESSKEY: myKey
    REGISTRY_STORAGE_S3_SECRETKEY: mySecret
    REGISTRY_STORAGE_S3_BUCKET: docker.registry.bucket
    REGISTRY_STORAGE_S3_ROOTDIRECTORY: registry/data
  volumes:
    - /home/docker/certs:/certs

And when I try to run sudo docker-compose up -d I get this error message:

registry_1 | panic: multiple storage drivers specified in configuration or environment: s3, filesystem

It seems like I'm missing something in my environment to explicitly choose s3 but it's not clear from the docs how to do this.

Answer 1

I was trying to override the storage configuration by using ENV vars. This workaround did the job (in json format):

{
    "REGISTRY_STORAGE": "s3",
    "REGISTRY_STORAGE_S3_REGION": <REGION>,
    "REGISTRY_STORAGE_S3_BUCKET": <BUCKET_NAME>,
    "REGISTRY_STORAGE_S3_ROOTDIRECTORY": <ROOT_PATH>,
    "REGISTRY_STORAGE_S3_ACCESSKEY": <KEY>,
    "REGISTRY_STORAGE_S3_SECRETKEY": <SECRET>
}

It looks like by defining REGISTRY_STORAGE we override the one in config.yml.

Answer 2

There is REGISTRY_STORAGE environment variable missing. Need to be added to the "env" block.