Skip to content

docs: Specify DOCKER_TLS_CERTDIR for DinD >= 19.03

Moritz Schlarb requested to merge (removed):moschlar-master-patch-63900 into master

What does this MR do?

Add an example for the Gitlab CI config when using Docker-in-Docker >= 19.03 with TLS enabled

Since Docker-in-Docker is using TLS by default from 19.03 on, we need to specify a place where the daemon and the client both can store and access the corresponding certificates. Since the /builds directory is shared between the runner and the service container, we just use it for this purpose.

Related issues

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.

Merge request reports