Official Repository

Last pushed: 9 days ago
Short Description 
Containerized docker registry
Full Description 
Supported tags and respective Dockerfile links

For more information about this image and its history, please see the relevant manifest file (library/registry). This image is updated via pull requests to the docker-library/official-images GitHub repo.

For detailed information about the virtual/transfer sizes and individual layers of each of the above supported tags, please see the registry/ file in the docker-library/docs GitHub repo.

Docker Registry

The tags >= 2 refer to the new registry.

Older tags refer to the deprecated registry.

Run the Registry

Run the registry docker container: Quick version

  • run the registry: docker run -p 5000:5000 -v <HOST_DIR>:/tmp/registry-dev registry
  • Modify your docker startup line/script: add "-H tcp:// -H unix:///var/run/docker.sock --insecure-registry <REGISTRY_HOSTNAME>:5000"

Recommended: run the registry docker container

$ docker run \
         -e SETTINGS_FLAVOR=s3 \
         -e AWS_BUCKET=acme-docker \
         -e STORAGE_PATH=/registry \
         -e AWS_KEY=AKIAHSHB43HS3J92MXZ \
         -e AWS_SECRET=xdDowwlK7TJajV1Y7EoOZrmuPEJlHYcNP2k4j49T \
         -e SEARCH_BACKEND=sqlalchemy \
         -p 5000:5000 \

NOTE: The container will try to allocate the port 5000. If the port is already taken, find out which container is already using it by running docker ps.


If you are interested in commercial support, the Docker Trusted Registry provides an image registry, LDAP/Active Directory integration, security certificates, and more in a solution that includes commercial support.

Supported Docker versions

This image is officially supported on Docker version 1.9.1.

Support for older versions (down to 1.6) is provided on a best-effort basis.

Please see the Docker installation documentation for details on how to upgrade your Docker daemon.

User Feedback Documentation

Documentation for this image is stored in the registry/ directory of the docker-library/docs GitHub repo. Be sure to familiarize yourself with the repository's file before attempting a pull request.


If you have any problems with or questions about this image, please contact us through a GitHub issue.

You can also reach many of the official image maintainers via the #docker-library IRC channel on Freenode.


You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.

Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.

Docker Pull Command

Comments (35)
a year ago

It's possible to build last tag 0.7.1 ?

a year ago

Yes, please, 0.7.1 :D

a year ago

Please update this image ... you've skipped 0.7.1 already so please upload 0.7.2

a year ago

How to search images in the own registry we started?

a year ago

You guys probably have noticed, but 0.7.1, 0.7.2 and 0.7.3 have been there for a week or so already =) Just wanted to clarify for people who just arrived!

@lemonbar, you'll want to look at enabling the indexing module and using the /v1/search endpoint. HTH!

a year ago

Running the 0.7.3 image, there seems to be something strange with the libraries inside the running container that prevents nsenter from creating a bash process:

nsenter --target 21011 --mount --uts --ipc --net --pid /bin/bash

/bin/bash: error while loading shared libraries: /lib/x86_64-linux-gnu/ invalid ELF header

Can anyone reproduce?

a year ago

@jjneely: Nope... can not be reproduced:

<code>core@localhost ~ $ sudo nsenter -t 3988 --mount --uts --ipc --net --pid /bin/bash
groups: cannot find name for group ID 11
root@71f544be5723:/# </code>

a year ago

How to view the list of images pushed inside the registry ????

a year ago

where is the 0.9.0 image? it was released yesterday

a year ago

Any idea on how to fix this error?

2014-11-17 19:02:06 [13] [ERROR] Exception in worker process:
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/gunicorn/", line 507, in spawn_worker
File "/usr/local/lib/python2.7/dist-packages/gunicorn/workers/", line 193, in init_process
super(GeventWorker, self).init_process()
File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/", line 435, in do_execute
cursor.execute(statement, parameters)

OperationalError: (OperationalError) table version already exists u'\nCREATE TABLE version (\n\tid INTEGER NOT NULL, \n\tPRIMARY KEY (id)\n)\n\n' ()