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

Docker executor cannot pull image from private registry #14

Open
kk17 opened this issue Mar 9, 2016 · 0 comments
Open

Docker executor cannot pull image from private registry #14

kk17 opened this issue Mar 9, 2016 · 0 comments

Comments

@kk17
Copy link

kk17 commented Mar 9, 2016

I use gitlab-ci-multi-runner:1.0.4, here is code snippet of my docker-compose.yml:

GitlabCIMultiRunner:
  image: sameersbn/gitlab-ci-multi-runner:1.0.4
  volumes:
    # share Docker unix sock
    - /var/run/docker.sock:/var/run/docker.sock
    # share docker config for using docker registry
    - ~/.docker:/root/.docker

I get this problem when doing ci build, Docker executor cannot pull image from private registry:

Using Docker executor with image docker.163.com/pyenv-common:latest ...
Pulling docker image my-private-registry/pyenv-common:latest ...
WARNING: Cannot pull the latest version of image docker.163.com/pyenv-common:latest : Error: image pyenv-common:latest not found
WARNING: Locally found image will be used instead.

Running on runner-b0913476-project-2-concurrent-0 via 5f6196c6c24c...

I change the shared docker config folder to:

 - ~/.docker:/home/gitlab_ci_multi_runner/.docker

but this still not work.

And I change to use the GitLab official Runner image, it work.

image: gitlab/gitlab-runner:latest

I want to know what is the difference and how to make this gitlab-ci-multi-runner work as the offical one.

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

No branches or pull requests

1 participant