docker-registry v2.2.0 S3 config not overwritten

I’m having an issue trying to start a docker registry service with S3 backend. Its acting very strangely. If I launch like this:

docker run -d -e SETTINGS_FLAVOR=s3 -e AWS_BUCKET=sotic-docker-registry -e STORAGE_PATH=/registry -e AWS_REGION=eu-west-1 -e AWS_KEY=***** -e AWS_SECRET=***** -e STORAGE_REDIRECT=true -e SEARCH_BACKEND=sqlalchemy -p 5000:5000 registry:2.2.0

As suggested by other topics on here, I don’t get an overridden config file.

  • Why rotated nginx in Docker log file not release in filesystem?
  • Running on runner-…-concurrent-0 via … runner for LONG time never ends
  • docker-compose to run django with mongodb
  • Multiple threads inside docker container
  • Dockerized Node js app does not start
  • Headless protractor not sharding tests
  • Running docker exec on the container and looking at the /etc/docker/registry/config.yml seems to suggest I’m still using the local storage.

    root@5727b353e734:/# vi /etc/docker/registry/config.yml
    version: 0.1
        service: registry
            blobdescriptor: inmemory
            rootdirectory: /var/lib/registry
        addr: :5000
            X-Content-Type-Options: [nosniff]
        enabled: true
        interval: 10s
        threshold: 3

    Any pointers?

  • How to forward all ports in docker container
  • How to change docker ip address on centos 7?
  • Connection refused on docker container
  • Docker linking container
  • Cannot install inside docker container
  • Docker HttpExceptionRequest Can't GET from inside container
  • One Solution collect form web for “docker-registry v2.2.0 S3 config not overwritten”

    It seems the /etc/docker/registry/config.json file never gets touched in the default image. None of the overrides seem to work.

    The answer is to build your own registry image and ADD a config.json with the required components in it.


    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.