fcrozat/distribution
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Remove docs.docker.com "include" directives

Browse Source 
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This commit is contained in:
Sebastiaan van Stijn 2021-04-22 12:57:35 +02:00
parent ef8966aacd
commit ff0c463f2b
No known key found for this signature in database
GPG Key ID: 76698F39D527CE8C
22 changed files with 0 additions and 44 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/compatibility.md
View File

@ -4,8 +4,6 @@ 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

2
docs/deploying.md
View File

@ -4,8 +4,6 @@ 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.

2
docs/deprecated.md
View File

@ -4,8 +4,6 @@ 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.

2
docs/garbage-collection.md
View File

@ -4,8 +4,6 @@ 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.

2
docs/help.md
View File

@ -4,8 +4,6 @@ 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 about development, you can reach us on the #distribution channel in the CNCF Slack.
If you want to report a bug:

2
docs/index.md
View File

@ -6,8 +6,6 @@ redirect_from:
title: Docker Registry
---
{% include registry.md %}
## What it is
The Registry is a stateless, highly scalable server side application that stores

2
docs/insecure.md
View File

@ -4,8 +4,6 @@ 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

2
docs/introduction.md
View File

@ -4,8 +4,6 @@ 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.

2
docs/notifications.md
View File

@ -4,8 +4,6 @@ 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

2
docs/recipes/apache.md
View File

@ -4,8 +4,6 @@ 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.

2
docs/recipes/index.md
View File

@ -4,8 +4,6 @@ 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.

2
docs/recipes/mirror.md
View File

@ -6,8 +6,6 @@ redirect_from:
- /engine/admin/registry_mirror/
---
{% include registry.md %}
## Use-case
If you have multiple instances of Docker running in your environment, such as

2
docs/recipes/nginx.md
View File

@ -6,8 +6,6 @@ redirect_from:
- /registry/nginx/
---
{% include registry.md %}
## Use-case
People already relying on a nginx proxy to authenticate their users to other

2
docs/recipes/osx-setup-guide.md
View File

@ -4,8 +4,6 @@ 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.

2
docs/storage-drivers/azure.md
View File

@ -4,8 +4,6 @@ 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](https://azure.microsoft.com/en-us/services/storage/) for object storage.
## Parameters

2
docs/storage-drivers/filesystem.md
View File

@ -4,8 +4,6 @@ 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

2
docs/storage-drivers/gcs.md
View File

@ -4,8 +4,6 @@ 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

2
docs/storage-drivers/index.md
View File

@ -6,8 +6,6 @@ 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

2
docs/storage-drivers/inmemory.md
View File

@ -4,8 +4,6 @@ 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

2
docs/storage-drivers/oss.md
View File

@ -4,8 +4,6 @@ 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.

2
docs/storage-drivers/s3.md
View File

@ -4,8 +4,6 @@ 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.

2
docs/storage-drivers/swift.md
View File

@ -4,8 +4,6 @@ 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.