From 063416007408525cb2598dd38b164baf883fdb56 Mon Sep 17 00:00:00 2001 From: Milos Gajdos Date: Fri, 1 Sep 2023 11:04:33 +0100 Subject: [PATCH] Remove outdated docs This commit removes Registry v1 -> Registry v2 migration guide as Registry v1 was deprecated long time ago and is no long longer supported. We also remove some references to "Future" roadmap which are wildly outdated, too. Signed-off-by: Milos Gajdos --- docs/migration.md | 28 ---------------------------- docs/spec/api.md | 13 ------------- docs/spec/api.md.tmpl | 13 ------------- 3 files changed, 54 deletions(-) delete mode 100644 docs/migration.md diff --git a/docs/migration.md b/docs/migration.md deleted file mode 100644 index e46441cb..00000000 --- a/docs/migration.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -published: false ---- - -# Migrating a 1.0 registry to 2.0 - -TODO: This needs to be revised in light of Olivier's work - -A few thoughts here: - -There was no "1.0". There was an implementation of the Registry API V1 but only a version 0.9 of the service was released. -The image formats are not compatible in any way. One must convert v1 images to v2 images using a docker client or other tool. -One can migrate images from one version to the other by pulling images from the old registry and pushing them to the v2 registry. - ------ - -The Docker Registry 2.0 is backward compatible with images created by the earlier specification. If you are migrating a private registry to version 2.0, you should use the following process: - -1. Configure and test a 2.0 registry image in a sandbox environment. - -2. Back up up your production image storage. - - Your production image storage should reside on a volume or storage backend. - Make sure you have a backup of its contents. - -3. Stop your existing registry service. - -4. Restart your registry with your tested 2.0 image. diff --git a/docs/spec/api.md b/docs/spec/api.md index 8eb42b19..9b34163c 100644 --- a/docs/spec/api.md +++ b/docs/spec/api.md @@ -52,19 +52,6 @@ specification, details of the protocol will be left to a future specification. Relevant header definitions and error codes are present to provide an indication of what a client may encounter. -#### Future - -There are features that have been discussed during the process of cutting this -specification. The following is an incomplete list: - -- Immutable image references -- Multiple architecture support -- Migration from v2compatibility representation - -These may represent features that are either out of the scope of this -specification, the purview of another specification or have been deferred to a -future version. - ### Use Cases For the most part, the use cases of the former registry API apply to the new diff --git a/docs/spec/api.md.tmpl b/docs/spec/api.md.tmpl index 7fcc566e..7629d236 100644 --- a/docs/spec/api.md.tmpl +++ b/docs/spec/api.md.tmpl @@ -52,19 +52,6 @@ specification, details of the protocol will be left to a future specification. Relevant header definitions and error codes are present to provide an indication of what a client may encounter. -#### Future - -There are features that have been discussed during the process of cutting this -specification. The following is an incomplete list: - -- Immutable image references -- Multiple architecture support -- Migration from v2compatibility representation - -These may represent features that are either out of the scope of this -specification, the purview of another specification or have been deferred to a -future version. - ### Use Cases For the most part, the use cases of the former registry API apply to the new