Run a Docker Registry Backed by IBM SoftLayer Object Storage
June 22, 2014
A Docker registry stores the images and the graph for a set of repositories. The shiny, new Docker Hub uses one to store all of the wonderful repositories created by the Docker community. You too can run a registry by spinning up an instance of the official Docker registry image. In fact, it's trivial to get a registry running using host local disk:
[email protected]$ mkdir -p /mnt/registry [email protected]$ sudo docker run -d -p 5000:5000 -v /mnt/registry:/tmp/registry registry
Such a standalone registry can prove useful, say, in quickly deploying containers on a cloud private network. Of course, for serious applications, you'll want more robust storage than local disk, especially on virtual hosts. Thankfully, the registry project defines an interface for storage drivers and even ships with one for S3.
In this post, I'll show you how to configure the OpenStack Swift registry storage driver so that it works with IBM SoftLayer Object Storage. At the end of the post, you'll have a registry container running on a SoftLayer VM and persisting Docker repositories in SoftLayer Object Storage. I won't cover adding authentication to your registry, but the result can still prove useful in a secure environment.
In the first three sections, I'll describe how to setup object storage and deploy a VM using the SoftLayer Control panel. Skip to building the
registry-swift image if you are already familiar with SoftLayer and can't wait to get to the interesting Docker bits.
Open the Control Panel
Start by visiting the SoftLayer Control Panel and logging-in using your account credentials. If you don't have a SoftLayer account and want to try the steps in this tutorial, you can get a public cloud instance free for 30 days to run the registry. However, you'll need to pay for object storage.
Setup Object Storage
If you haven't already, order object storage by clicking the Storage drop down, selecting Object Storage, and then clicking Order Object Storage. Review and accept the storage rates.
When notified that object storage is available for your account, return to the object storage page and select a data center to host the content of your registry. On the data center page, click the View Credentials link and note the private authentication endpoint URL, username, and API key for your account. You'll need them to configure the Docker registry.
Finally, click the Add Container link. Give your container the name docker-registry and click OK.
Provision a VM
Next visit the Devices drop down, select Device List, and click the Order Devices link. Pick an hourly virtual server instance and configure it as follows:
- Select any data center you wish.
- Choose the Ubuntu 14.04 minimal install (64-bit).
- Click Continue Your Order.
- Put the following URL in the Provision scripts URL box: https://bit.ly/1l2xaWE (It installs the latest stable version of Docker from the Docker, Inc. apt-get repository when SoftLayer provisions your VM.)
- Choose a public SSH key to add to your VM. (If you don't have one in your account, you can use root password generated when you order your VM for this experiment.)
- Give your server any host and domain name you wish. (You'll be using its public IP address.)
- Read and accept the Terms and Conditions.
- Click Finalize Your Order.
When your VM is ready, get its public IP address from the Devices → Device List. If you configured it with a public key, use the corresponding private key to SSH into it as the root user. If not, use the generated root password also shown in the Device List entry for your instance.
The official registry container image does not include the Swift storage driver. Nor does it include an option in the sample configuration to override the driver's
swift_auth_version from its default value of
2. You need both to work with SoftLayer Object Storage. You can get both by building your own image starting from the official registry image.
On your VM, create a
Dockerfile and fill it with the following commands.
# start from a registry release known to work FROM registry:0.7.3 # get the swift driver for the registry RUN pip install docker-registry-driver-swift==0.0.1 # SoftLayer uses v1 auth and the sample config doesn't have an option # for it so inject one RUN sed -i '91i\ swift_auth_version: _env:OS_AUTH_VERSION' /docker-registry/config/config_sample.yml
Build the Dockerfile like so, replacing
parente with your Docker username.
[email protected]$ docker build -t parente/registry-swift:0.7.3 .
With the image in hand, you're ready to launch an instance. Doing so requires that you set quite a few options which I explain after the command below:
[email protected]$ docker run -it -d \ -e SETTINGS_FLAVOR=swift \ -e OS_AUTH_URL='https://dal05.objectstorage.service.networklayer.com/auth/v1.0' \ -e OS_AUTH_VERSION=1 \ -e OS_USERNAME='my_master_account:my_account' \ -e OS_PASSWORD='my_api_key' \ -e OS_CONTAINER='docker-registry' \ -e GUNICORN_WORKERS=8 \ -p 127.0.0.1:5000:5000 \ parente/registry-swift:0.7.3
SETTINGS_FLAVOR=swiftto use the Swift storage driver.
OS_AUTH_URLto the private object storage authentication endpoint you noted earlier.
OS_AUTH_VERSION=1to match the version used by SoftLayer.
OS_USERNAMEto the object storage username you noted earlier.
OS_PASSWORDto the object Ssorage API key you noted earlier.`
OS_CONTAINER=docker-registryto the name of the object storage container you created earlier.
- Optionally, set
GUNICORN_WORKERSto the number of Flask workers you want the registry to run, overriding the default of
- Set the interface and port on which the registry should listen. Above, I've set it to listen on localhost only for demo purposes. You could, for example, set it to listen on the private IP of the VM (i.e.,
-p 10.108.66.125:5000:5000) or even all interfaces to allow public access (i.e.,
- Finally, remember to change the
parenteto match the username you used when building your image.
Push to Test
With the registry running, you can now test it by pushing something to it. Since you have the registry image you just built on hand, you can use that. First, tag it with the registry IP and port as a prefix, again replacing
parente with your username.
[email protected]$ docker tag parente/registry-swift:0.7.3 127.0.0.1:5000/parente/registry-swift:0.7.3
Now push it.
[email protected]$ docker push 127.0.0.1:5000/parente/registry-swift:0.7.3
If all goes well, you should should see the results of the push in the
docker-registry container in the Object Storage control panel. Because the registry stores all Docker repository data and metadata in the storage layer, you can kill, restart, and migrate your registry Docker container at will.
Since the registry runs in a Docker container, you can easily run multiple instances for your many projects, each one configured to persist in a separate object storage container. You might also try running multiple instances configured with the same storage container name, say for better scalability, though I have not tested what happens in concurrent overwrite scenarios in such a configuration. (Please let me know if you do.) Finally, you can front your registry with a web proxy supporting basic auth to enable select users to push to your registry.