diff options
| author | Steve Azzopardi <sazzopardi@gitlab.com> | 2019-06-21 08:56:34 +0200 |
|---|---|---|
| committer | Steve Azzopardi <sazzopardi@gitlab.com> | 2019-06-25 08:23:42 +0200 |
| commit | 137e37d3e9c5369230d609a2f1553d2c65b2a747 (patch) | |
| tree | f5ac7eb02d630e40cca373d6a8eacce4955f1ae8 | |
| parent | f904971e5fefff92b0cc467a4dc4483ba68b6e6c (diff) | |
| download | gitlab-ce-docs/63418-docs-feedback-update-for-11-11-1-feature-flag.tar.gz | |
Add note about Docker socket mountingdocs/63418-docs-feedback-update-for-11-11-1-feature-flag
When using `docker:dind` service and the Runner has the socket mounted
as well it will lead to the following error:
```
Failed to load listeners: can't create unix socket /var/run/docker.sock:
device or resource busy
```
reference https://gitlab.com/gitlab-org/gitlab-ce/issues/63418
| -rw-r--r-- | doc/ci/docker/using_docker_build.md | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/doc/ci/docker/using_docker_build.md b/doc/ci/docker/using_docker_build.md index b4c4bea6447..efdcaf5a6f5 100644 --- a/doc/ci/docker/using_docker_build.md +++ b/doc/ci/docker/using_docker_build.md @@ -205,7 +205,14 @@ An example project using this approach can be found here: <https://gitlab.com/gi ### Use Docker socket binding -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. +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. + +NOTE: **Note:** +If you bind the Docker socket [when using GitLab Runner 11.11 or +newer](https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/1261), +you can no longer use `docker:dind` as a service because volume bindings +are done to the services as well, making these incompatible. In order to do that, follow the steps: |