Remote Repositories

Overview

To configure a remote repository, in the Admin module, go to Repositories | Remote and click it to display the Edit Repository screen.

Common Basic Settings

The following are fully described in the Common Settings page.

Additional Basic Settings

URL

The URL for the remote repository. Currently only HTTP and HTTPS URLs are supported.

Offline

If set, this repository will be considered offline and no attempts will be made to fetch artifacts from it.

For more details, please refer to Single Repository Offline below.

Page Contents

Read More

Advanced Settings

Type-Specific Basic Settings

Docker has additional Basic settings.

Handling Offline Scenarios

JFrog Container Registry supports offline repository management at two levels:

Single Repository: One or more specific remote repositories need to be offline.
Global: The whole organization is disconnected from remote repositories

Single Repository Offline

If a remote repository goes offline for any reason, JFrog Container Registry can be configured to ignore it by setting the Offline checkbox in the Admin tab under Repositories | Remote. In this case, only artifacts from this repository that are already present in the cache are used. No further attempt will be made to fetch remote artifacts.

Global Offline Mode

This is common in organizations that require a separate, secured network and are disconnected from the rest of the world (for example, military or financial institutions) .

In this case, remote repositories serve as caches only and do not proxy remote artifacts.

You can enable Global Offline Mode by setting the corresponding checkbox in the Admin tab under Configuration | General.

Browsing Remote Repositories

In some cases, JFrog Container Registry proxy supports remote browsing. In these cases, you can browse the contents of these repositories directly from the JFrog Container Registry UI. In the example below, the contents of the Helm repository is shown.