Skip to content
Snippets Groups Projects

Try to get the offline docs to be similar - Container Scanning

Merged Nicole Schwartz requested to merge Secure-offline-scanners-docs into master
All threads resolved!
@@ -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
#### Make GitLab Container Scanning analyzer images available inside your Docker registry
#### Make GitLab Container Scanning analyzer images available inside your Docker registry
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):
For Container Scanning, import and host the following images from `registry.gitlab.com` to your
- [arminc/clair-db vulnerabilities database](https://hub.docker.com/r/arminc/clair-db)
offline [local Docker container registry](../../packages/container_registry/index.md):
- GitLab klar analyzer: `registry.gitlab.com/gitlab-org/security-products/analyzers/klar`
 
- [arminc/clair-db vulnerabilities database](https://hub.docker.com/r/arminc/clair-db)
 
- GitLab klar analyzer: `registry.gitlab.com/gitlab-org/security-products/analyzers/klar`
The process for importing Docker images into a local offline Docker registry depends on
The process for importing Docker images into a local offline Docker registry depends on
**your network security policy**. Please consult your IT staff to find an accepted and approved
**your network security policy**. Please consult your IT staff to find an accepted and approved
@@ -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)
Note that these scanners are [updated periodically](../index.md#maintenance-and-update-of-the-vulnerabilities-database)
with new definitions, so consider if you are able to make periodic updates yourself.
with new definitions, so consider if you are able to make periodic updates yourself.
You can read more specific steps on how to do this [below.](#automating-container-scanning-vulnerability-database-updates-with-a-pipeline)
You can read more specific steps on how to do this [below](#automating-container-scanning-vulnerability-database-updates-with-a-pipeline).
For details on saving and transporting Docker images as a file, see Docker's documentation on
For details on saving and transporting Docker images as a file, see Docker's documentation on
[`docker save`](https://docs.docker.com/engine/reference/commandline/save/), [`docker load`](https://docs.docker.com/engine/reference/commandline/load/),
[`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
#### Automating Container Scanning vulnerability database updates with a pipeline
#### Automating Container Scanning vulnerability database updates with a pipeline
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:
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 do it manually each time. You can use the following
 
`.gitlab-yml.ci` as a template:
```yaml
```yaml
image: docker:stable
image: docker:stable
Loading