Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Container Registry to Artifact Registry Server Side GTM

We've received email over the past year about the move to Artifact Registry.

We have an sGTM implementation that was auto-provisioned running on App Engine, and various forums have declared that these will be auto migrated.

I ran the script 

gcloud container images list-gcr-usage \
    --project=PROJECT

on my system, and it returns ACTIVE. 

Either automigration isn't happening, hasn't happened, or won't happen.

The instructions to migrate seem straightforward. Just run the script: 

gcloud artifacts docker upgrade migrate \
    --projects=PROJECTS

 The instructions say to monitor to see if there is a problem. However, there isn't much information on what to do if there is a problem. I've got a large installation, and we can't have downtime.

I'd like some advice on how to manage the upgrade.

Thanks,



0 1 118
1 REPLY 1

Hi @Alison_TT,

Welcome to the Google Cloud community!

Migrating from Google Container Registry (GCR) to Artifact Registry (AR) is a crucial move that needs careful planning to avoid service disruptions. Here's a simple approach to handle the migration smoothly:

1. Assess the Current State

  • Verify Migration Status: Run the command gcloud container images list-gcr-usage --project=my-proj to check the status of your images. If it returns "ACTIVE," your images are still in GCR.
  • Understand Auto-Migration: While Google has initiated auto-migration for some users, it may not apply to all projects. It's crucial to confirm whether your project is included in this process.

2. Plan the Migration:

  • Choose the Migration Method: For large installations, using the automatic migration tool is recommended to reduce complexity and minimize downtime. This tool automates the transfer of images from GCR to AR.
  • Prepare for Manual Migration (if necessary): If automatic migration isn't feasible, manual migration involves pulling images from GCR and pushing them to AR. This method requires careful planning to avoid service disruptions.

3. Execute the Migration Automatic Migration

  • Use the command: gcloud artifacts docker upgrade migrate --projects=my-project
  • Monitor the process for any errors or warnings. The command will provide feedback on the migration status.

For more in-depth analysis, you can contact Google Cloud Support. When contacting them, please provide comprehensive details and include screenshots. This will help them better understand and address your issue.

Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.