docker/migrator

Tool to migrate Docker images from Docker Hub or v1 registry to a v2 registry

https://hub.docker.com/r/docker/migrator/

Usage

docker run -it \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -e V1_REGISTRY=v1.registry.fqdn \
  -e V2_REGISTRY=v2.registry.fqdn \
  docker/migrator

Environment Variables

The following environment variables can be set:

Required

• V1_REGISTRY - DNS hostname of your v1 registry or Docker Hub (Do not include https://)
  • If migrating images from Docker Hub, use docker.io
• V2_REGISTRY - DNS hostname of your v2 registry (Do not include https://)

Optional

• ERROR_ACTION - Sets the default action on error for pushes and pulls
  • prompt - (Default) Prompt for user input as to what action to take on error
  • retry - Retry the failed action on error (may cause infinite loop of failure)
  • skip - Log the error and continue migration on error
  • abort - Abort the migration on error
• USER_PROMPT - Sets the default action for user prompts (non-error)
  • true - (Default) Prompts user for input/validation
  • false - Skips user prompt and automatically proceeds
• NO_LOGIN
  • true - Skips docker login for both the v1 and v2 registries
  • false - (Default) Prompts user to login to the v1 and v2 registries
• V1_NO_LOGIN
  • true - Skips docker login for the v1 registry
  • false - (Default) Prompts user to login to the v1 registry
• V2_NO_LOGIN
  • true - Skips docker login for the v2 registry
  • false - (Default) Prompts user to login to the v2 registry
• USE_INSECURE_CURL
  • true - Allows curl to perform insecure SSL connections for querying APIs
  • false - (Default) Require curl to perform secure SSL connections for querying APIs
• USE_HTTP
  • true - Allows curl to connect to both the v1 and v2 registries over HTTP
  • false - (Default) Requires curl to connect to v1 and v2 registries over HTTPS
• V1_USE_HTTP
  • true - Allows curl to connect to v1 registry running over HTTP
  • false - (Default) Requires curl to connect to v1 registry over HTTPS
• V2_USE_HTTP
  • true - Allows curl to connect to v2 registry running over HTTP
  • false - (Default) Requires curl to connect to v2 registry over HTTPS
• DOCKER_HUB_ORG - Docker Hub organization name to migrate images from
  • Defaults to the username used to login to Docker Hub if not provided
• V1_REPO_FILTER - Search filter to limit the scope of the repositories to migrate (uses grep basic regular expression interpretation)
  • Note: This only filters the repositories returned from the source registry search API, not the individual tags
• Custom CA certificate and Client certificate support - for custom CA and/or client certificate support to your v1 and/or v2 registries, you should utilize a volume to share them into the container by adding the following to your run command:
  • -v /etc/docker/certs.d:/etc/docker/certs.d:ro
• V1_USERNAME - Username used for docker login to the v1 registry
• V1_PASSWORD - Password used for docker login to the v1 registry
• V1_EMAIL - Email used for docker login to the v1 registry
• V2_USERNAME - Username used for docker login to the v2 registry
• V2_PASSWORD - Password used for docker login to the v2 registry
• V2_EMAIL - Email used for docker login to the v2 registry

Note: You must use all three variables (V1_USERNAME, V1_PASSWORD, and V1_EMAIL or V2_USERNAME, V2_PASSWORD, and V2_EMAIL) for the given automated docker login to function properly. Omitting one will prompt the user for input of all three.

• KEEP_LOCAL_CACHE
  • true - Prevents migrator from cleaning up the local image cache

Prerequisites

This migration tool assumes the following:

• You have a v1 registry (or Docker Hub) and you are planning on migrating to a v2 registry
• The new v2 registry can either be running using a different DNS name or the same DNS name as the v1 registry - both scenarios work in this case. If you are utilizing the same DNS name for your new v2 registry, set both V1_REGISTRY and V2_REGISTRY to the same value.

It is suggested that you run this container on a Docker engine that is located near your registry as you will need to pull down every image from your v1 registry (or Docker Hub) and push them to the v2 registry to complete the migration. This also means that you will need enough disk space on your local Docker engine to temporarily store all of the images.

How Migration Works

The migration occurs using an automated script inside of the Docker container. Running using the above usage will work as expected.

1. Login to the v1 registry or Docker Hub (Optional)

• If you do not have authentication enabled, leave the username blank when prompted

2. Query the v1 registry or Docker Hub for a list of all repositories
3. With the list of images, query the v1 registry or Docker Hub for all tags for each repository. This becomes the list of all images with tags that you need to migrate
4. Using a Docker engine, pull all images (including each tag)
5. Once all images are pulled, there are a few options for next steps:
6. If the same DNS record will be used for the v1 and v2 registries: * Have user switch the DNS record over to the new server's IP or if same box to be used, stop the v1 registry and start the v2 registry
7. If a different DNS record will be used for the v1 and v2 registries: * Re-tag all images to change the tagging from the old DNS record to the new one
8. Login to the v2 registry (Optional)

• If you do not have authentication enabled, leave the username blank when prompted

7. Push all images and tags to the v2 registry
8. Verify v1 to v2 image migration was successful (not yet implemented)
9. Cleanup local docker engine to remove images

Logging Migration Output

If you need to log the output from migrator, add 2>&1 | tee migration.log to the end of the command shown above to capture the output to a file of your choice.