Docker registry image ready for production
554
This Docker image contains a Docker registry you can use to run your own, private repository in your organization. Please see this blog post for details.
In the default configuration (local), the registry container uses a local directory in the file system to store images. This directory is configured to use a separate volume /docker-registry-storage which can be mapped by the docker run -v parameter -- see Makefile target start-registry. In order to correctly run parallel work threads, the configuration file config.yml contains a secret_key.
In case you would like to customize the Docker image, please clone the corresponding GitHub Repository and follow the instructions below. There is also a Vagrant file included in case you are on a system not directly supported by Docker.
This Docker registry image is prepared for customizing the storage backend, the secret_key, and the flavor to run:
config.yml.template. For S3 there are already the necessary keys which only need to be filled. Then run
make -B config.yml registry@@SEC_KEY@@ with your key of choice. If you keep the file unchanged, the command above will automatically create a random key using openssl.FLAVOR to select the desired flavor. See below.Run from Docker Index -- you can omit the -e parameter to run the local flavor:
docker run --name registry -d -e FLAVOR=<flavor> -p 5000:5000 -v <absolute path to storage>:/docker-registry-storage lukaspustina/registry
Run from GitHub repository:
local by running make start-registryFLAVOR=<your flavor> make -e start-registrymake stop-registrymake cleanContent type
Image
Digest
sha256:4e33ce9bd…
Size
150.4 MB
Last updated
about 11 years ago
docker pull lukaspustina/docker-registry