Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

With gitlab-runner version 10.x package, docker-volumes is wrongly set #8

Closed
nperron opened this issue Nov 3, 2017 · 0 comments · Fixed by #9
Closed

With gitlab-runner version 10.x package, docker-volumes is wrongly set #8

nperron opened this issue Nov 3, 2017 · 0 comments · Fixed by #9

Comments

@nperron
Copy link

nperron commented Nov 3, 2017

Actually, on your 'master' branch, the role does not correctly register the runner with docker executor.

The parameter --docker-volumes is not correctly set since you try to use a mutli-parameter with comma-separeted.

--docker-volumes use its argument as one parameter. If others parameters needed, we have to set several times --docker-volumes like this:

gitlab-runner register --non-interactive -url https://gitlab.com/ --registration-token xxxxxxx --description test-runner --tag test --executor docker --docker-image debian:stable-backports --docker-volumes "/var/run/docker.sock:/var/run/docker.sock" --docker-volumes "/cache"

In order to have:

  [runners.docker]
    tls_verify = false
    image = "debian:stable-backports"
    privileged = false
    disable_cache = false
    volumes = ["/var/run/docker.sock:/var/run/docker.sock", "/cache"]
    shm_size = 0

Instead, actually we've got this:

  [runners.docker]
    tls_verify = false
    image = "debian:stable-backports"
    privileged = false
    disable_cache = false
    volumes = ["[", "/cache"]
    shm_size = 0
@markv markv mentioned this issue Dec 1, 2017
@riemers riemers closed this as completed in #9 Dec 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant