5df53c0681
Making metadata: - more consistent - more specific (fixed copy pasting) - refine coverage Insecure information cleanup Removing no longer used files: - mkdocs is gone - the registry diagram is not used, and is a bit silly :) Minor fixes Fixing links Recipes: - harmonized code sections style to the rest of the docs - harmonized recipe "style" - listing new recipes Enhance deploying Signed-off-by: Olivier Gambier <olivier@docker.com>
66 lines
No EOL
2 KiB
Markdown
66 lines
No EOL
2 KiB
Markdown
<!--[metadata]>
|
|
+++
|
|
title = "Docker Registry"
|
|
description = "High-level overview of the Registry"
|
|
keywords = ["registry, on-prem, images, tags, repository, distribution"]
|
|
[menu.main]
|
|
parent="smn_registry"
|
|
+++
|
|
<![end-metadata]-->
|
|
|
|
# Docker Registry
|
|
|
|
## What it is
|
|
|
|
The Registry is a stateless, highly scalable server side application that stores and lets you distribute Docker images.
|
|
The Registry is open-source, under the permissive [Apache license](http://en.wikipedia.org/wiki/Apache_License).
|
|
|
|
## Why use it
|
|
|
|
You should use the Registry if you want to:
|
|
|
|
* tightly control where your images are being stored
|
|
* fully own your images distribution pipeline
|
|
* integrate image storage and distribution tightly into your in-house development workflow
|
|
|
|
## Alternatives
|
|
|
|
Users looking for a zero maintenance, ready-to-go solution are encouraged to head-over to the [Docker Hub](https://hub.docker.com), which provides a free-to-use, hosted Registry, plus additional features (organization accounts, automated builds, and more).
|
|
|
|
Users looking for a commercially supported version of the Registry should look into [Docker Trusted Registry](https://docs.docker.com/docker-trusted-registry/).
|
|
|
|
## Requirements
|
|
|
|
The Registry is compatible with Docker engine **version 1.6.0 or higher**.
|
|
If you really need to work with older Docker versions, you should look into the [old python registry](https://github.com/docker/docker-registry).
|
|
|
|
## TL;DR
|
|
|
|
Start your registry
|
|
|
|
docker run -d -p 5000:5000 --name registry registry:2
|
|
|
|
Pull (or build) some image from the hub
|
|
|
|
docker pull ubuntu
|
|
|
|
Tag the image so that it points to your registry
|
|
|
|
docker tag ubuntu localhost:5000/myfirstimage
|
|
|
|
Push it
|
|
|
|
docker push localhost:5000/myfirstimage
|
|
|
|
Pull it back
|
|
|
|
docker pull localhost:5000/myfirstimage
|
|
|
|
Now stop your registry and remove all data
|
|
|
|
docker stop registry && docker rm -v registry
|
|
|
|
## Next
|
|
|
|
You should now read the [detailed introduction about the registry](introduction.md), or jump directly to [deployment instructions](deploying.md).
|
|
|