GCR to ACR Container Migration

LAST UPDATED MARCH 21, 2025

READER NOTE

Due to Google's policy change, GCR will stop accepting writes on March 18, 2025, and will disable all read/write services on April 20, 2025. This will impact new d3agent/d3executor usage.
Since these containers do not store local data, updates pose no risk of data loss.

GCR = Google Container Registry | ACR = Azure Container Registry

Two solutions are available for the GCR to ACR migration.

Solution A: Update the existing d3agent and d3executor image addresses to use ACR.
Solution B: Perform a fresh installation.
Solution C: Use the automatic upgrade function to upgrade to the ACR. The web application version must be 17.0 or higher.

SOLUTION C*

The entire process is handled by the D3 technical support team. Customers are only required to review the final outcome.

Pre-Migration Checklist

Before migration, confirm ACR connectivity using the following commands:

ACR is accessible if the output includes "404 Not Found."*

Verify Docker Image Pull from Microsoft ACR:

BASH

docker pull mcr.microsoft.com/azurelinux/base/python:3

The setup is correct if the output includes "Status: Downloaded newer image for mcr.microsoft.com/azurelinux/base/python:3."*