From 014de87479154e3e5e9b94ee15cbcabc19f0795a Mon Sep 17 00:00:00 2001 From: Achilleas Pipinellis Date: Mon, 9 Sep 2019 05:47:49 +0000 Subject: [PATCH] Document workaround for SAST failures There's an error that occurs when the Docker version used to run the SAST job is 19.03.00, and the job will fail. Advise the users what to do in case they bump into this. --- .../dependency_scanning/index.md | 19 ++++++++++--------- doc/user/application_security/sast/index.md | 19 ++++++++++--------- 2 files changed, 20 insertions(+), 18 deletions(-) diff --git a/doc/user/application_security/dependency_scanning/index.md b/doc/user/application_security/dependency_scanning/index.md index fa2df667031..89526c08e7e 100644 --- a/doc/user/application_security/dependency_scanning/index.md +++ b/doc/user/application_security/dependency_scanning/index.md @@ -46,6 +46,10 @@ To run a Dependency Scanning job, you need GitLab Runner with the executor running in privileged mode. If you're using the shared Runners on GitLab.com, this is enabled by default. +CAUTION: **Caution:** +If you use your own Runners, make sure that the Docker version you have installed +is **not** `19.03.00`. See [troubleshooting information](#error-response-from-daemon-error-processing-tar-file-docker-tar-relocation-error) for details. + ## Supported languages and package managers The following languages and dependency managers are supported. @@ -343,14 +347,11 @@ You can search the [gemnasium-db](https://gitlab.com/gitlab-org/security-product to find a vulnerability in the Gemnasium database. You can also [submit new vulnerabilities](https://gitlab.com/gitlab-org/security-products/gemnasium-db/blob/master/CONTRIBUTING.md). - +This error occurs when the Docker version used to run the SAST job is `19.03.00`. +You are advised to update to Docker `19.03.01` or greater. Older versions are not +affected. Read more in +[this issue](https://gitlab.com/gitlab-org/gitlab-ee/issues/13830#note_211354992 "Current SAST container fails"). diff --git a/doc/user/application_security/sast/index.md b/doc/user/application_security/sast/index.md index 15a21bb82e0..956d3ef7c8c 100644 --- a/doc/user/application_security/sast/index.md +++ b/doc/user/application_security/sast/index.md @@ -51,6 +51,10 @@ To run a SAST job, you need GitLab Runner with the executor running in privileged mode. If you're using the shared Runners on GitLab.com, this is enabled by default. +CAUTION: **Caution:** +If you use your own Runners, make sure that the Docker version you have installed +is **not** `19.03.00`. See [troubleshooting information](#error-response-from-daemon-error-processing-tar-file-docker-tar-relocation-error) for details. + ## Supported languages and frameworks The following table shows which languages, package managers and frameworks are supported and which tools are used. @@ -350,14 +354,11 @@ Once a vulnerability is found, you can interact with it. Read more on how to For more information about the vulnerabilities database update, check the [maintenance table](../index.md#maintenance-and-update-of-the-vulnerabilities-database). - +This error occurs when the Docker version used to run the SAST job is `19.03.00`. +You are advised to update to Docker `19.03.01` or greater. Older versions are not +affected. Read more in +[this issue](https://gitlab.com/gitlab-org/gitlab-ee/issues/13830#note_211354992 "Current SAST container fails").