vbatts/registry
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
registry/docs/migration.md
Mary Anthony cf9b4ab5e9 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-09 17:50:46 -07:00

1 KiB
Raw Blame History

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 Service 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.