Merge pull request #11085 from usha-mandya/registry-patch
Add note on Docker Hub
This commit is contained in:
commit
5636e34037
@ -4,6 +4,8 @@ keywords: registry, manifest, images, tags, repository, distribution, digest
|
||||
title: Registry compatibility
|
||||
---
|
||||
|
||||
{% include registry.md %}
|
||||
|
||||
## Synopsis
|
||||
If a manifest is pulled by _digest_ from a registry 2.3 with Docker Engine 1.9
|
||||
and older, and the manifest was pushed with Docker Engine 1.10, a security check
|
||||
|
@ -4,6 +4,8 @@ keywords: registry, on-prem, images, tags, repository, distribution, deployment
|
||||
title: Deploy a registry server
|
||||
---
|
||||
|
||||
{% include registry.md %}
|
||||
|
||||
Before you can deploy a registry, you need to install Docker on the host.
|
||||
A registry is an instance of the `registry` image, and runs within Docker.
|
||||
|
||||
|
@ -4,6 +4,8 @@ keywords: registry, manifest, images, signatures, repository, distribution, dige
|
||||
title: Docker Registry deprecation
|
||||
---
|
||||
|
||||
{% include registry.md %}
|
||||
|
||||
This document details functionality or components which are deprecated within
|
||||
the registry.
|
||||
|
||||
|
@ -4,6 +4,8 @@ keywords: registry, garbage, images, tags, repository, distribution
|
||||
title: Garbage collection
|
||||
---
|
||||
|
||||
{% include registry.md %}
|
||||
|
||||
As of v2.4.0 a garbage collector command is included within the registry binary.
|
||||
This document describes what this command does and how and why it should be used.
|
||||
|
||||
|
@ -4,6 +4,8 @@ keywords: registry, on-prem, images, tags, repository, distribution, help, 101,
|
||||
title: Get help
|
||||
---
|
||||
|
||||
{% include registry.md %}
|
||||
|
||||
If you need help, or just want to chat, you can reach us:
|
||||
|
||||
- on the [Docker forums](https://forums.docker.com/c/open-source-projects/opensrcreg).
|
||||
|
@ -6,6 +6,8 @@ redirect_from:
|
||||
title: Docker Registry
|
||||
---
|
||||
|
||||
{% include registry.md %}
|
||||
|
||||
## What it is
|
||||
|
||||
The Registry is a stateless, highly scalable server side application that stores
|
||||
|
@ -4,6 +4,8 @@ keywords: registry, on-prem, images, tags, repository, distribution, insecure
|
||||
title: Test an insecure registry
|
||||
---
|
||||
|
||||
{% include registry.md %}
|
||||
|
||||
While it's highly recommended to secure your registry using a TLS certificate
|
||||
issued by a known CA, you can choose to use self-signed certificates, or use
|
||||
your registry over an unencrypted HTTP connection. Either of these choices
|
||||
|
@ -4,6 +4,8 @@ keywords: registry, on-prem, images, tags, repository, distribution, use cases,
|
||||
title: About Registry
|
||||
---
|
||||
|
||||
{% include registry.md %}
|
||||
|
||||
A registry is a storage and content delivery system, holding named Docker
|
||||
images, available in different tagged versions.
|
||||
|
||||
|
@ -4,6 +4,8 @@ keywords: registry, on-prem, images, tags, repository, distribution, notificatio
|
||||
title: Work with notifications
|
||||
---
|
||||
|
||||
{% include registry.md %}
|
||||
|
||||
The Registry supports sending webhook notifications in response to events
|
||||
happening within the registry. Notifications are sent in response to manifest
|
||||
pushes and pulls and layer pushes and pulls. These actions are serialized into
|
||||
|
@ -4,6 +4,8 @@ keywords: registry, on-prem, images, tags, repository, distribution, authenticat
|
||||
title: Authenticate proxy with apache
|
||||
---
|
||||
|
||||
{% include registry.md %}
|
||||
|
||||
## Use-case
|
||||
|
||||
People already relying on an apache proxy to authenticate their users to other services might want to leverage it and have Registry communications tunneled through the same pipeline.
|
||||
|
@ -4,6 +4,8 @@ keywords: registry, on-prem, images, tags, repository, distribution, recipes, ad
|
||||
title: Recipes overview
|
||||
---
|
||||
|
||||
{% include registry.md %}
|
||||
|
||||
This list of "recipes" provides end-to-end scenarios for exotic or otherwise advanced use-cases.
|
||||
These recipes are not useful for most standard set-ups.
|
||||
|
||||
|
@ -6,6 +6,8 @@ redirect_from:
|
||||
- /engine/admin/registry_mirror/
|
||||
---
|
||||
|
||||
{% include registry.md %}
|
||||
|
||||
## Use-case
|
||||
|
||||
If you have multiple instances of Docker running in your environment, such as
|
||||
|
@ -6,6 +6,8 @@ redirect_from:
|
||||
- /registry/nginx/
|
||||
---
|
||||
|
||||
{% include registry.md %}
|
||||
|
||||
## Use-case
|
||||
|
||||
People already relying on a nginx proxy to authenticate their users to other
|
||||
|
@ -4,6 +4,8 @@ keywords: registry, on-prem, images, tags, repository, distribution, macOS, reci
|
||||
title: macOS setup guide
|
||||
---
|
||||
|
||||
{% include registry.md %}
|
||||
|
||||
## Use-case
|
||||
|
||||
This is useful if you intend to run a registry server natively on macOS.
|
||||
|
@ -4,6 +4,8 @@ keywords: registry, service, driver, images, storage, azure
|
||||
title: Microsoft Azure storage driver
|
||||
---
|
||||
|
||||
{% include registry.md %}
|
||||
|
||||
An implementation of the `storagedriver.StorageDriver` interface which uses [Microsoft Azure Blob Storage](http://azure.microsoft.com/en-us/services/storage/) for object storage.
|
||||
|
||||
## Parameters
|
||||
|
@ -4,6 +4,8 @@ keywords: registry, service, driver, images, storage, filesystem
|
||||
title: Filesystem storage driver
|
||||
---
|
||||
|
||||
{% include registry.md %}
|
||||
|
||||
An implementation of the `storagedriver.StorageDriver` interface which uses the local filesystem.
|
||||
|
||||
## Parameters
|
||||
|
@ -4,6 +4,8 @@ keywords: registry, service, driver, images, storage, gcs, google, cloud
|
||||
title: Google Cloud Storage driver
|
||||
---
|
||||
|
||||
{% include registry.md %}
|
||||
|
||||
An implementation of the `storagedriver.StorageDriver` interface which uses Google Cloud for object storage.
|
||||
|
||||
## Parameters
|
||||
|
@ -6,6 +6,8 @@ redirect_from:
|
||||
title: Docker Registry storage driver
|
||||
---
|
||||
|
||||
{% include registry.md %}
|
||||
|
||||
This document describes the registry storage driver model, implementation, and explains how to contribute new storage drivers.
|
||||
|
||||
## Provided drivers
|
||||
|
@ -4,6 +4,8 @@ keywords: registry, service, driver, images, storage, in-memory
|
||||
title: In-memory storage driver (testing only)
|
||||
---
|
||||
|
||||
{% include registry.md %}
|
||||
|
||||
For purely tests purposes, you can use the `inmemory` storage driver. This
|
||||
driver is an implementation of the `storagedriver.StorageDriver` interface which
|
||||
uses local memory for object storage. If you would like to run a registry from
|
||||
|
@ -4,6 +4,8 @@ keywords: registry, service, driver, images, storage, OSS, aliyun
|
||||
title: Aliyun OSS storage driver
|
||||
---
|
||||
|
||||
{% include registry.md %}
|
||||
|
||||
An implementation of the `storagedriver.StorageDriver` interface which uses
|
||||
[Aliyun OSS](https://www.alibabacloud.com/product/oss) for object storage.
|
||||
|
||||
|
@ -4,6 +4,8 @@ keywords: registry, service, driver, images, storage, S3
|
||||
title: S3 storage driver
|
||||
---
|
||||
|
||||
{% include registry.md %}
|
||||
|
||||
An implementation of the `storagedriver.StorageDriver` interface which uses
|
||||
Amazon S3 or S3 compatible services for object storage.
|
||||
|
||||
|
@ -4,6 +4,8 @@ keywords: registry, service, driver, images, storage, swift
|
||||
title: OpenStack Swift storage driver
|
||||
---
|
||||
|
||||
{% include registry.md %}
|
||||
|
||||
An implementation of the `storagedriver.StorageDriver` interface that uses
|
||||
[OpenStack Swift](http://docs.openstack.org/developer/swift/) for object
|
||||
storage.
|
||||
|
Loading…
Reference in New Issue
Block a user