CI/CD Error about dockerswarm.rocks HOT 5 CLOSED

So I used interactive registration shown in GitLab guidelines, which worked until recently when I discovered same problem again.
It appears that not only Docker has to be mounted, but although runner must be configured to use it.

Probably, docker socket mounting is not enough once you register more than one runner on same container/service/volume.
So to make it work, make sure that in runner's config.toml (can be found in volume's root), for all you runners volumes property has docker socket:

# runners defintion
[[runners]]
  volumes = ["/var/run/docker.sock:/var/run/docker.sock", "/cache"]
  # other properties not mentioned here

P.S.: realized that with the help of Portainer, settled up after @tiangolo 's guide Thank You!

from dockerswarm.rocks.

It seems like your GitLab runner doesn't have access to Docker. Make sure you create it in a manager node and with the Docker sock volume mounted.

from dockerswarm.rocks.

Assuming the original issue was solved, it will be automatically closed now. But feel free to add more comments or create new issues.

from dockerswarm.rocks.

I have the same issue, with Docker socket being mounted.
That's how Binds property of container looks like:

"Binds": [
                "/var/run/docker.sock:/var/run/docker.sock",
                "gitlab-runner:/etc/gitlab-runner"
            ],

update: I tried a bit different approach (follow instructions from here after creation of docker container for ci runner), but still have same issue.

Exact error from job logs:

 $ docker login -u gitlab-ci-token -p $CI_JOB_TOKEN $CI_REGISTRY
 WARNING! Using --password via the CLI is insecure. Use --password-stdin.
 error during connect: Post http://docker:2375/v1.40/auth: dial tcp: lookup docker on 213.133.98.98:53: no such host
 ERROR: Job failed: exit code 1

It could be worth noting, that I'm using the official GitLab website (not self-hosted).
And I found a few similar issues env vars display their values (not just name). IP was different too, and it seems to point at my hosting provider...

from dockerswarm.rocks.

That was my mistake - I didn't mount Docker socket.

from dockerswarm.rocks.