Using the latest version?
JFrog Container Registry Guide


Skip to end of metadata
Go to start of metadata

Overview

JFrog Container Registry supports import and export of data at two levels:

At system level, JFrog Container Registry can export and import the whole JFrog Container Registry server: configuration, security information, stored data and metadata. The format used is identical to the System Backup format. This is useful when manually running backups and for migrating and restoring a complete JFrog Container Registry instance (as an alternative to using database level backup and restore).

At repository level, JFrog Container Registry can export and import data and metadata stored in a repository. This is useful when moving store data, including its metadata between repositories and for batch population of a repository.

Page Contents


System Import and Export

Excluding builds

You can exclude builds only using the ExportSystem. This is not available from the JFrog Container Registry UI.

Note: The System Import and Export feature is not available for JFrog Container Registry Cloud users.

To access import and export of your entire system, in the Admin module, select Import & Export | System

 

Maintaining security entities on system import

JFrog Container Registry maintains all security entities (users, groups, permissions and access tokens) when doing a system import. Previously, these entities would be removed along with existing configurations, repositories and artifacts.

 

Target Export Dir
The target directory for the exported files. You may browse your file system to select the directory
Exclude Content

Export: When set, repository binaries are excluded from the export.

Import: When set, binaries and metadata are excluded from the import. Only builds and configuration files are imported.

Exclude Metadata

When set, repository metadata are excluded from the import/export.

Docker repositories must have metadata

For Docker repositories to work they must have their metadata intact. Therefore, if you have Docker repositories, make sure that Exclude Metadata is not checked when doing a system export or import.

Exclude Builds
When set, all builds are excluded from the export
Create a Zip Archive (Slow and CPU Intensive!)
When set, creates and exports to a Zip archive
Output Verbose Log

When set, lowers the log level to "debug" and redirects the output from the standard log to the import-export log.

Monitoring the log

You can monitor the log in the JFrog Container Registry Log Files page.


The source/target of the import/export operations are folders (Zip archives are not recommended) on the JFrog Container Registry server itself.

You can use the built-in server-side browsing inside JFrog Container Registry to select server-side source/target folders:


Importing or exporting a large amount of data may be time consuming. During the import/export operation you can browse away from the page and sample the System Logs to monitor progress.

 

Repositories Import and Export

Note: Importing repositories is supported for all users whereas exporting repositories is only available for non-Cloud users.


To access import and export of repositories, in the Admin tab, select Import & Export | Repositories

Export

When exporting, you need to specify the following parameters:

Target Local Repository

You can specify a single repository to export, or All Repositories 

Export Path on Server
The export target directory on your server
Exclude Metadata
When set, repository metadata are excluded from the export.
Output Verbose Log

When set, lowers the log level to "debug" and redirects the output from the standard log to the import-export log.

Monitoring the log

You can monitor the log in the System Logs page.


Import Task list

You can import repositories from a server side folder, or by zipping a repository and uploading it to JFrog Container Registry.


When importing, you need to specify the following parameters:

Target Local Repository
You can specify a single repository to import, or All Repositories. The repository layout should be different depending on your selection. Please refer to Import Layout
Server Path for Import
The import source directory on your server
Exclude Metadata
When set, repository metadata are excluded from the import
Output Verbose Log

When set, lowers the log level to "debug" and redirects the output from the standard log to the import-export log.

Monitoring the log

You can monitor the log in the System Logs page.

Don't exclude metadata for Docker

To work with a Docker repository, it must have its metadata intact. Therefore, when importing to/exporting from a Docker repository make sure that Exclude Metadata is not checked.


Import Layout

When importing a single repository, the file structure within the import folder (or zip file) should be as follows:

IMPORT_FOLDER/ZIP_FILE
|
|--LIB_DIR_1

When importing all repositories, the file structure within the import folder should be as follows:



When importing all repositories, you need to ensure that the names of the directories representing the repositories in the archive match the names of the target repositories in JFrog Container Registry.




  • No labels