Try to get the offline docs to be similar - Container Scanning
All threads resolved!
All threads resolved!
Compare changes
@@ -231,9 +231,11 @@ in an offline environment if you prefer using only locally available Docker imag
@@ -231,9 +231,11 @@ in an offline environment if you prefer using only locally available Docker imag
For Container Scanning, import and host the following images from `registry.gitlab.com` to your "offline" [local Docker container registry](../../packages/container_registry/index.md):
@@ -241,7 +243,7 @@ process by which external resources can be imported or temporarily accessed.
@@ -241,7 +243,7 @@ process by which external resources can be imported or temporarily accessed.
Note that these scanners are [updated periodically](../index.md#maintenance-and-update-of-the-vulnerabilities-database)
You can read more specific steps on how to do this [below.](#automating-container-scanning-vulnerability-database-updates-with-a-pipeline)
[`docker save`](https://docs.docker.com/engine/reference/commandline/save/), [`docker load`](https://docs.docker.com/engine/reference/commandline/load/),
@@ -269,7 +271,10 @@ Container Scanning can be executed on an offline GitLab Ultimate installation us
@@ -269,7 +271,10 @@ Container Scanning can be executed on an offline GitLab Ultimate installation us
It can be worthwhile to set up a [scheduled pipeline](../../../ci/pipelines/schedules.md) to automatically build a new version of the vulnerabilities database on a preset schedule. Automating this with a pipeline means you won't have to manually do it each time. You can use the following `.gitlab-yml.ci` as a template: