Do not use docker-in-docker term when mounting docker socket from host (#17)

Author: kangasta

docs/examples/jenkins/ansible-kubernetes/README.md

@@ -8,7 +8,7 @@ You will need a running Kubernetes cluster, that supports services with `LoadBal
 
 ## Preparing the Jenkins instance
 
-The pipeline provided by this example can be added to any Jenkins instance you have administrator access and can run pipeline stages with docker agent. For example, Jenkins configuration from [Docker-in-Docker](../dind-jenkins/) example can be used.
+The pipeline provided by this example can be added to any Jenkins instance you have administrator access and can run pipeline stages with docker agent. For example, Jenkins configuration from [Jenkins with access to hosts Docker engine](../jenkins-host-docker/) example can be used.
 
 We will use secret file to configure credentials for managing the target Kubernetes cluster. To create the secret file credential, open _Global credentials_ from _Jenkins_ credentials store from [Manage Jenkins > Manage Credentials](http://localhost:8080/credentials/) and click _Add Credentials_ from the left side menu.
 

docs/examples/jenkins/build-status-pipelines/README.md

@@ -4,7 +4,7 @@ This example contains pipelines to produce builds with success, unstable, failed
 
 ## Preparing the Jenkins instance
 
-The pipeline provided by this example can be added to any Jenkins instance you have administrator access. For example, Jenkins configuration from [Docker-in-Docker](../dind-jenkins/) example can be used.
+The pipeline provided by this example can be added to any Jenkins instance you have administrator access. For example, Jenkins configuration from [Jenkins with access to hosts Docker engine](../jenkins-host-docker/) example can be used.
 
 In order to be able to run the seed project we will need [Job DSL](https://plugins.jenkins.io/job-dsl/) plugin. Install the plugin through Available tab in [Manage Jenkins > Manage Plugins](http://localhost:8080/pluginManager/available).
 

docs/examples/jenkins/dind-jenkins/Dockerfile renamed to docs/examples/jenkins/jenkins-host-docker/Dockerfile

@@ -1,29 +1,31 @@
-# Jenkins with hosts Docker socket
+# Jenkins with access to hosts Docker engine
 
 Note that by default each of the example docker compose configurations will create their own volumes for the data. This might not be what you want. In order to use the same volumes for every docker compose configuration, run docker compose with `-p` (or `--project-name`) option. This can also be done by setting `COMPOSE_PROJECT_NAME` environment variable:
 
 ```sh
 export COMPOSE_PROJECT_NAME=jenkins
 ```
 
-## Jenkins image with Docker-in-Docker support
+## Jenkins image with Docker client
 
 To be able run Docker commands from inside the Jenkins container, we will need to install the Docker client. This can be done with a suitable Dockerfile:
 
 ```Dockerfile title="Dockerfile"
---8<-- "docs/examples/jenkins/dind-jenkins/Dockerfile"
+--8<-- "docs/examples/jenkins/jenkins-host-docker/Dockerfile"
 ```
 
-When running this container, we will want to define ports and volumes. To do this, we will use a `docker-compose.yml` configuration:
+## Jenkins container with access to hosts Docker engine
+
+When running Jenkins in a container, we will want to define ports and volumes. To do this, we will use a `docker-compose.yml` configuration:
 
 ```yaml title="docker-compose.yml"
---8<-- "docs/examples/jenkins/dind-jenkins/docker-compose.yml"
+--8<-- "docs/examples/jenkins/jenkins-host-docker/docker-compose.yml"
 ```
 
-These files are available in the repository that provides this website. In order to run Jenkins container with Docker-in-Docker support, `cd` into `docs/examples/jenkins/dind-jenkins` directory and run `docker compose up`.
+These files are available in the repository that provides this website. In order to run Jenkins container with Docker-in-Docker support, `cd` into `docs/examples/jenkins/jenkins-host-docker` directory and run `docker compose up`.
 
 ```sh
-cd docs/examples/jenkins/dind-jenkins
+cd docs/examples/jenkins/jenkins-host-docker
 
 # If you want to see logs in the current terminal
 docker compose up --build

docs/examples/jenkins/dind-jenkins/README.md renamed to docs/examples/jenkins/jenkins-host-docker/README.md

@@ -4,7 +4,7 @@ This directory provides an example of a Jenkins pipeline that executes Robot Fra
 
 ## Preparing the Jenkins instance
 
-The pipeline provided by this example can be added to any Jenkins instance you have administrator access and can run pipeline stages with docker agent. For example, Jenkins configuration from [Docker-in-Docker](../dind-jenkins/) example can be used.
+The pipeline provided by this example can be added to any Jenkins instance you have administrator access and can run pipeline stages with docker agent. For example, Jenkins configuration from [Jenkins with access to hosts Docker engine](../jenkins-host-docker/) example can be used.
 
 In order to be able to run the pipeline we will need [Docker Pipeline](https://plugins.jenkins.io/docker-workflow/) and [Robot Framework](https://plugins.jenkins.io/robot/) plugins. Install these plugins through _Available_ tab in [Manage Jenkins > Manage Plugins](http://localhost:8080/pluginManager/available) and restart the Jenkins instance after these plugins have been installed. The restart can be done, for example, from the plugins page or by restarting the container with `docker compose down` and `docker compose up`.
 

docs/examples/jenkins/dind-jenkins/docker-compose.yml renamed to docs/examples/jenkins/jenkins-host-docker/docker-compose.yml

@@ -1,9 +1,9 @@
 # Jenkins and SonarQube
 
-This example uses the same Jenkins configuration as the [Docker-in-Docker](../dind-jenkins/) example. If you did any configuration in [dind-jenkins](../dind-jenkins/) directory, sync the project names with `-p`/`--project-name` option or `COMPOSE_PROJECT_NAME` environment variable to use the same volumes. For example:
+This example uses the same Jenkins configuration as the [Jenkins with access to hosts Docker engine](../jenkins-host-docker/) example. If you did any configuration in [jenkins-host-docker](../jenkins-host-docker/) directory, sync the project names with `-p`/`--project-name` option or `COMPOSE_PROJECT_NAME` environment variable to use the same volumes. For example:
 
 ```sh
-# Replace jenkins with dind-jenkins, if you used default project name in dind-jenkins directory.
+# Replace jenkins with jenkins-host-docker, if you used default project name in jenkins-host-docker directory.
 
 # With -p/--project-name argument:
 docker compose -p jenkins up -d

docs/examples/jenkins/parallel-robot-pipeline/README.md

@@ -1,7 +1,7 @@
 version: "3"
 services:
   jenkins:
-    build: ../dind-jenkins/
+    build: ../jenkins-host-docker/
     ports:
     # Web user interface
     - 8080:8080

docs/examples/jenkins/sonarqube-jenkins/README.md

@@ -13,7 +13,7 @@ nav:
 - Docker:
   - ./examples/docker/docker-on-wsl/README.md
 - Jenkins:
-  - ./examples/jenkins/dind-jenkins/README.md
+  - ./examples/jenkins/jenkins-host-docker/README.md
   - ./examples/jenkins/ansible-kubernetes/README.md
   - ./examples/jenkins/build-status-pipelines/README.md
   - ./examples/jenkins/parallel-robot-pipeline/README.md