Container registries
Scan every new image that your GitLab container registry receives.
A container registry integration watches the images in a GitLab container registry. When an image gets a new tag, Portal adds the image as a Docker image asset if it isn’t one yet and runs an audit of the new tag. Auditor pulls the image with the integration’s token, so you don’t enter the registry credentials anywhere else.
GitLab is the only registry supported now. GitHub and Docker Hub are shown as Coming Soon.
Container registry integrations need a paid license. See License.
Connect
Open the settings, then Container Registries under Integrations, and click Add Container Registry.
- Choose the registry.
- Enter the GitLab URL and a personal access token with the
read_registryandread_apiscopes. The form links to the page where you create the token. - Enter the Registry domain, for example
registry.gitlab.com.
After you connect, Portal reads the tags that are already in the registry. They are listed on the integration’s page, and only tags that appear after this are scanned.
Choose when to scan
| Trigger | How it works |
|---|---|
| On webhook events | GitLab tells Portal when a CI job finishes, and the new tags of that project are scanned. Copy the Webhook URL from the integration’s page and add it to the project or group webhooks in GitLab with job events turned on. |
| On schedule | The registry is checked for new tags on a cron schedule. Webhook events are ignored, so you don’t need the webhook. |
Choose what to run
Job sequence sets the sequence that the audits of new tags run. Leave it empty to use each asset’s own sequence.
New images go to the default product, Unsorted. Move them to their products on the Assets page; the next tags are scanned in the product you chose.
Image tags
The integration’s page lists the tags that Portal has seen. Delete a tag from the list to scan it again the next time it is found.