forked from TrueCloudLab/distribution
267e231de0
* Fix incorrect links in compose section there's a bug causing wrapped links to not work, and replacing some links to point to the .md file, so that IDE's can check if the anchors are valid. Also replaced some links to point to their new location. Signed-off-by: Sebastiaan van Stijn <github@gone.nl> * engine/swarm: update links Signed-off-by: Sebastiaan van Stijn <github@gone.nl> * Fix various broken links There's a bug in the "jekyll-relative-links" plugin that causes wrapped links to not work. Also replacing some links to point to the .md file, so that IDE's can check if the anchors are valid. Finally, replaced some links to point to their new locations, so that users don't get redirected.. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
76 lines
2.2 KiB
Markdown
76 lines
2.2 KiB
Markdown
---
|
|
description: High-level overview of the Registry
|
|
keywords: registry, on-prem, images, tags, repository, distribution
|
|
redirect_from:
|
|
- /registry/overview/
|
|
title: Docker Registry
|
|
---
|
|
|
|
> Looking for Docker Trusted Registry?
|
|
>
|
|
> Docker Trusted Registry (DTR) is a commercial product that enables complete
|
|
> image management workflow, featuring LDAP integration, image signing,
|
|
> security scanning, and integration with Universal Control Plane. DTR is
|
|
> offered as an add-on to Docker Enterprise subscriptions of Standard or
|
|
> higher.
|
|
>
|
|
> [Go to Docker Trusted Registry](/ee/dtr/){: class="button outline-btn" }
|
|
|
|
## 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](/ee/dtr/).
|
|
|
|
## Requirements
|
|
|
|
The Registry is compatible with Docker engine **version 1.6.0 or higher**.
|
|
|
|
## Basic commands
|
|
|
|
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 image 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 container stop registry && docker container rm -v registry
|
|
|
|
## Next
|
|
|
|
You should now read the [detailed introduction about the registry](introduction.md),
|
|
or jump directly to [deployment instructions](deploying.md).
|