diff options
| author | Mark Pundsack <markpundsack@users.noreply.github.com> | 2016-06-07 22:25:33 -0700 |
|---|---|---|
| committer | Mark Pundsack <markpundsack@users.noreply.github.com> | 2016-06-13 22:06:13 -0700 |
| commit | d9cbe019866843132225d440754a20da0e937d00 (patch) | |
| tree | 44807b7785f089f9f387dafbe9a1e25ddc29b39c | |
| parent | 6841e76b45b44da9f749538dbae2bb1fc63d8ee4 (diff) | |
| download | gitlab-ce-d9cbe019866843132225d440754a20da0e937d00.tar.gz | |
Moar commas
| -rw-r--r-- | doc/ci/docker/using_docker_build.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/ci/docker/using_docker_build.md b/doc/ci/docker/using_docker_build.md index a5f37366265..4620eeac2b6 100644 --- a/doc/ci/docker/using_docker_build.md +++ b/doc/ci/docker/using_docker_build.md @@ -76,7 +76,7 @@ The second approach is to use the special Docker image with all tools installed (`docker` and `docker-compose`) and run the build script in context of that image in privileged mode. -In order to do that follow the steps: +In order to do that, follow the steps: 1. Install [GitLab Runner](https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/#installation). @@ -151,7 +151,7 @@ An example project using this approach can be found here: https://gitlab.com/git The third approach is to bind-mount `/var/run/docker.sock` into the container so that docker is available in the context of that image. -In order to do that follow the steps: +In order to do that, follow the steps: 1. Install [GitLab Runner](https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/#installation). |