kotovalexarian-likes-gitlab
/
gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Add note about Docker socket mounting 

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
This commit is contained in:
Steve Azzopardi 2019-06-21 08:56:34 +02:00
parent f904971e5f
commit 137e37d3e9
No known key found for this signature in database
GPG Key ID: B6FAD416292DEF2B
1 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/ci/docker/using_docker_build.md
View File

@ -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: