registry/docs/migration.md

<!--[metadata]>
+++
draft = "true"
+++
<![end-metadata]-->

# 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.
Updating for Hugo Updating for tooling tests Updating with the new sed scripts to protect links updating with new image Updating with comments Signed-off-by: Mary Anthony <mary@docker.com> 2015-06-08 00:58:53 +00:00			`<!--[metadata]>`
			`+++`
			`draft = "true"`
			`+++`
			`<![end-metadata]-->`

Breaking out README Adding new material Adding in template chomped in error Cover install/deploy in README Adding in Stephen's comments Fixing you tabs! Updating with commentary from pr Updating with last minute comments Signed-off-by: Mary Anthony <mary@docker.com> 2015-04-02 15:11:19 +00:00			`# 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.`

			`-----`

Fixes #391 for registry top page Fixes #390 to add building link to README Docker Registry Service to Docker Registry Signed-off-by: Mary Anthony <mary@docker.com> 2015-04-19 00:06:51 +00:00			`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:`
Breaking out README Adding new material Adding in template chomped in error Cover install/deploy in README Adding in Stephen's comments Fixing you tabs! Updating with commentary from pr Updating with last minute comments Signed-off-by: Mary Anthony <mary@docker.com> 2015-04-02 15:11:19 +00:00
			`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.`