> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scitix.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Import Images from External Repositories

> Import external images into the Registry in the selected Region using remote repositories and pull replication rules.

If the business images are stored in an external repository, you can first connect the repository and then create a pull rule to import matching images into a project in the target region. Before importing, confirm the repository path and tag range of the external images, as well as the target project, to avoid importing unnecessary versions.

Images can be imported from the following four types of registries:

* Docker Registry
* Docker Hub
* Google GCR
* Quay

## Pre-Action Confirmation

* A project in the target Region has been prepared to receive the image.
* The access URL for the external repository has been obtained. If the repository requires authentication, the corresponding credentials have also been obtained.

## Integrating External Repositories

1. Log in to the [GPU Cloud console](https://console.scitix.ai/gpu-cloud/home).

2. Go to **STORAGE > Registry** and select the target region.

3. Open the **Replication** tab.

4. Click to expand the **Registry Endpoints** section, then click **Add Endpoint**.

   ![Registry Endpoints Region](https://mintcdn.com/scitix-adfc65c2/zAestxkyOFggIEE8/gpu-cloud/registry/media/image-registry-endpoints.png?fit=max\&auto=format\&n=zAestxkyOFggIEE8\&q=85\&s=c9cfe685c61c5c080787d0e30ac886aa)

5. Enter the external repository connection information.

   | Configuration Item | Description |
   | - | - |
   | **Type** | Select the external repository type. |
   | **Name** | Set the endpoint name, which is used to identify the external repository in replication rules. We recommend using a name that indicates the repository source or purpose. |
   | **URL** | Enter the public access address of the external repository, for example, `https://example.com`. |
   | **Username** | Enter this when the external repository requires authentication. Leave it blank for public repositories. |
   | **Password** | Enter this when the external repository requires authentication. Leave it blank for public repositories. |

6. Click **Confirm**.

   Upon submission, the **URL** and credentials are validated. If the endpoint is unavailable, first check the external repository address, network connectivity, username, and password, then create an import rule. When synchronizing images across GPU Cloud regions, no external repository endpoint needs to be added.

## Create Synchronization Rule

1. On the **Replication** tab, click **Create Replication Rule**.

2. On the **Create Sync Rule** page, Configure the synchronization rule.

   Basic information:

   | Configuration Item | Description |
   | - | - |
   | **Sync Type** | Select **Pull Mode** to import images from an external registry to the registry in the current region. |
   | **Rule Name** | Enter a rule name. We recommend using a name that reflects the external registry, target project, or synchronization scope for easy identification in the rule list. |
   | **Description** | Enter a rule description as needed, such as the import source, applicable business, or maintainer. |

   Source Registry:

   | Configuration Item | Description |
   | - | - |
   | **Registry Endpoint** | Select an integrated external registry endpoint. If no endpoint is available, first complete external registry integration. |
   | **Namespace** | Enter or select the source project in the external registry. |
   | **Repository** | Enter or select the image repository to import. |
   | **Tag (Regex)** | Specify the tag matching criteria for import. `**` matches all tags; `1.0*` matches tags starting with `1.0`. We recommend matching only the version range required by your business. |

   Destination Registry:

   | Configuration Item | Description |
   | - | - |
   | **Region** | Select the target region to receive the image. |
   | **Namespace** | Enter or select the target project. After the import is complete, the image will be written to this project. |

   Synchronization rules:

   | Configuration Item | Description |
   | - | - |
   | **Override Mode** | When enabled, resources with the same name in the target project will be overwritten. Before enabling this option, confirm whether existing versions on the target side still need to be retained. |
   | **Enable Rule** | When enabled, the rule takes effect immediately after it is created. When not enabled, the rule is saved but synchronization does not start. |
   | **Trigger Mode** | Select a trigger method.<ul><li>**Event-driven**: Synchronization is triggered after the source image is pushed.</li><li>**Scheduled**: Imports are performed periodically according to a Cron expression.</li><li>**Manual**: Users manually trigger the import after creating the rule.</li></ul> |

3. Submit the rule and verify that the new rule appears in the rule list. When using manual triggering, you also need to synchronize the rule once.

## Confirm Import Results

View the execution records for the corresponding rule on the **Replication** tab.

* If any tasks fail, view the task logs and focus on checking the external repository connection, image path, label matching, and target project.
* After successful execution, switch to the **Projects** tab in the target region and confirm that the image has been added to the expected project.

## Related Documentation

If you need to distribute images from the current region to other repositories, see [Synchronize Images to Other Regions or Repositories](https://docs.scitix.ai/gpu-cloud/registry/sync-container-images.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.