You need to install Docker version 1.6.0 or newer.
Running on localhost
Start your registry:
You can now use it with docker. Get any image from the hub and tag it to point to your registry:
… then push it to your registry:
… then pull it back from your registry:
To stop your registry, you would:
By default, your registry data is persisted as a docker volume on the host filesystem. Properly understanding volumes is essential if you want to stick with a local filesystem storage. Specifically, you might want to point your volume location to a specific place in order to more easily access your registry data:
You should usually consider using another storage backend instead of the local filesystem. Use the storage configuration options to configure an alternate storage backend. Using one of these will allow you to more easily scale your registry, and leverage your storage redundancy and availability features.
Running a domain registry
While running on localhost has its uses, most people want their registry to be more widely available. To do so, the Docker engine requires you to secure it using TLS, which is conceptually very similar to configuring your web server with SSL.
Get a certificate
Assuming that you own the domain myregistrydomain.com, and that its DNS record points to the host where you are running your registry, you first need to get a certificate from a CA. Move and/or rename your crt file to: certs/domain.crt - and your key file to: certs/domain.key.
Make sure you stopped your registry from the previous steps, then start your registry again with TLS enabled:
You should now be able to access your registry from another docker host:
A certificate issuer may supply you with an intermediate certificate. In this case, you must combine your certificate with the intermediate’s to form a certificate bundle. You can do this using the cat command:
While rarely advisable, you may want to use self-signed certificates instead, or use your registry in an insecure fashion. You will find instructions here.
Except for registries running on secure local networks, registries should always implement access restrictions.
Native basic auth
The simplest way to achieve access restriction is through basic authentication (this is very similar to other web servers’ basic authentication mechanism). :warning: You cannot use authentication with an insecure registry. You have to configure TLS first for this to work.
First create a password file with one entry for the user “testuser”, with password “testpassword”:
Make sure you stopped your registry from the previous step, then start it again:
You should now be able to:
And then push and pull images as an authenticated user.
1. You may want to leverage more advanced basic auth implementations through a proxy design, in front of the registry. You will find an example of such design in the nginx proxy documentation.
2. Alternatively, the Registry also supports delegated authentication, redirecting users to a specific, trusted token server. That approach requires significantly more investment, and only make sense if you want to fully configure ACLs and more control over the Registry integration into your global authorization and authentication systems.
You will find background information here, and configuration information here. Beware that you will have to implement your own authentication service for this to work.
Managing with Compose
As your registry configuration grows more complex, dealing with it can quickly become tedious. It’s highly recommended to use Docker Compose to facilitate operating your registry. Here is a simple docker-compose.yml example that condenses everything explained so far:
You will find more specific and advanced informations in the following sections:
* Configuration reference
* Working with notifications
* Registry API
* Storage driver model