Fortinet black logo

Online Help

Docker Hub Add Registry Review

Copy Link
Copy Doc ID cf00dcb1-0886-11ed-bb32-fa163e15d75b:919824

Docker Hub Add Registry Review

After you pressed "Add Registry" or "Update Registry" in Add/Update Registry page, the following confirmation page will show the actual repositories that will be added to the registry. If you see all the repositories you want to add to the registry, press Confirm and Add to finish creating the registry.

If you do not see the repositories that you intend on adding to the registry, press the Back button to review and check the registry info entered.

Follow the guidelines below to configure and make the missing repositories accessible by Container Protection.

1. Check Organization Name

The repositories are accessible through the Docker Hub organization, make sure the correct Docker Hub Organization Name is entered

2. Check Docker Hub User Access Permission

The repositories that get to be added to Container Protection depends on the Docker Hub user access to the repositories. If the Docker Hub user is not granted with the permission to access the repository, Container Protection cannot detect the repository.

Scenario 1 - No Docker Hub user selected

Scenario 1 is when no Docker Hub user is selected, or " - " is selected, then only public repositories are detected.

Scenario 2 - Docker Hub User has no access to the repository.

Scenario 2 is a Docker Hub user is selected, but not all the repositories intended to be added show up in the list in confirmation page. This means that there are some repositories that the Docker Hub user does not have access to, thus Container Protection is unable to access those repositories.

Follow these steps to fix the permission issue:

Option 1: If the Docker Hub user is team member within a Docker Hub Organization, refer to Docker Hub Organization Access Configuration to grant repository access to the Docker Hub user.

Option 2: If the Docker Hub user is not within any Docker Hub organization, refer to Docker Hub Collaborators Access Configuration to make this Docker Hub user a collaborator.

3. Check Repository Name or Regex Rule

  1. Check on Repository field to make sure that the correct repository name is entered.
  2. Check on the Regex rule that you entered in the Repository field.
    1. Enter ".*" to capture all repositories.
    2. For example, to match the repository names: image-2x, image-3x, use "image\W\d\w".
    3. For more reference on using Regex, refer to https://www.regular-expressions.info/tutorial.html

Once you are done with review and re-configuration, press Add Registry or Update Registry to check if the repositories show up in the confirmation page.

.

Docker Hub Add Registry Review

After you pressed "Add Registry" or "Update Registry" in Add/Update Registry page, the following confirmation page will show the actual repositories that will be added to the registry. If you see all the repositories you want to add to the registry, press Confirm and Add to finish creating the registry.

If you do not see the repositories that you intend on adding to the registry, press the Back button to review and check the registry info entered.

Follow the guidelines below to configure and make the missing repositories accessible by Container Protection.

1. Check Organization Name

The repositories are accessible through the Docker Hub organization, make sure the correct Docker Hub Organization Name is entered

2. Check Docker Hub User Access Permission

The repositories that get to be added to Container Protection depends on the Docker Hub user access to the repositories. If the Docker Hub user is not granted with the permission to access the repository, Container Protection cannot detect the repository.

Scenario 1 - No Docker Hub user selected

Scenario 1 is when no Docker Hub user is selected, or " - " is selected, then only public repositories are detected.

Scenario 2 - Docker Hub User has no access to the repository.

Scenario 2 is a Docker Hub user is selected, but not all the repositories intended to be added show up in the list in confirmation page. This means that there are some repositories that the Docker Hub user does not have access to, thus Container Protection is unable to access those repositories.

Follow these steps to fix the permission issue:

Option 1: If the Docker Hub user is team member within a Docker Hub Organization, refer to Docker Hub Organization Access Configuration to grant repository access to the Docker Hub user.

Option 2: If the Docker Hub user is not within any Docker Hub organization, refer to Docker Hub Collaborators Access Configuration to make this Docker Hub user a collaborator.

3. Check Repository Name or Regex Rule

  1. Check on Repository field to make sure that the correct repository name is entered.
  2. Check on the Regex rule that you entered in the Repository field.
    1. Enter ".*" to capture all repositories.
    2. For example, to match the repository names: image-2x, image-3x, use "image\W\d\w".
    3. For more reference on using Regex, refer to https://www.regular-expressions.info/tutorial.html

Once you are done with review and re-configuration, press Add Registry or Update Registry to check if the repositories show up in the confirmation page.

.