Skip to content

Clarify docker-in-docker in Container Scanning docs

Achilleas Pipinellis requested to merge docs/container-scanning into master

What does this MR do?

Clarify the docker-in-docker "executor". There was a confusion, since there's not such executor, it's the privileged mode that we should highlight here.

Internal discussion about the confusion https://gitlab.slack.com/archives/C8S0HHM44/p1554769851515700.

PS. @eread I've since changed this to all new Secure docs that I'm passing at you :)

Related issues

none!

Author's checklist

  • Follow the Documentation Guidelines and Style Guide.
  • Link docs to and from the higher-level index page, plus other related docs where helpful.
  • Apply the ~Documentation label.

Review checklist

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.

1. Primary Reviewer

  • Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.

2. Technical Writer

  • Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.

3. Maintainer

  1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  2. Ensure a release milestone is set and that you merge the equivalent EE MR before the CE MR if both exist.
  3. If there has not been a technical writer review, create an issue for one using the Doc Review template.
Edited by 🤖 GitLab Bot 🤖

Merge request reports