Gitlab-Runner: Docker claims invalid credentials

Dear Users,

I am trying to get a gitlab-runner configured by using Auto Dev-ops executing Docker 1.13.1 on a client. The client, executing the runner with a user “gitrun”, is using Ubuntu 16.04 with gitlab-runner 10.5.0.

I am using an adopted Ubuntu docker image which is saved on the client.

When I am running the pipelines created by Auto DevOps, I get this message by the Gitlab-Server:

Running with gitlab-runner 10.5.0 (80b03db9)
  on gopigo-runner 6f59f053
Using Docker executor with image docker:git ...
Starting service docker:dind ...
Pulling docker image docker:dind ...
Using docker image sha256:6fc95ba0a7762a13d4db830df765c534ece1963f11093dfb8940f525b63084c3 for docker:dind ...
Waiting for services to be up and running...
Pulling docker image docker:git ...
Using docker image sha256:32b207609c8fe51719a5f424f84ffaa0cc2f185d1cb9591ba6bf81fcd9bd281a for docker:git ...
Running on runner-6f59f053-project-578-concurrent-0 via administrator-All-Series...
Fetching changes...
HEAD is now at ac5321c Empty Project
Checking out bffe3ef5 as aufbau...
Skipping Git submodules setup
$ # Auto DevOps variables and functions # collapsed multi-line command
$ setup_docker
$ build
Logging to GitLab Container Registry with CI credentials...
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
Error response from daemon: Get unauthorized: incorrect username or password
ERROR: Job failed: exit code 1

Also I logged in to Docker Hub from the running account (gitrun) and used correct credentials (User-ID instead of E-Mail) it does not work. I only want to use the local containers on the client, not any gitlab container registry.

The config.toml looks like that:

concurrent = 1
check_interval = 0

name = “gopigo-runner”
url = “https://gitlab.SERVER-ADDRESS/
token = “6f59f053c6fa8d987037f2f59e2051”
executor = “docker”
tls_verify = true
image = “ubuntuwithnlopt”
privileged = true
disable_cache = false
volumes = ["/cache"]
shm_size = 0

How can I fix that, as the Docker login on the machine confirms, that the login succeeded?

Thank you very much in advance.

Hello @lordsnyder,
I have the same problem. Did you found a solution?

Anybody find a solution ?

I Have the same issue.
Still no Solution?

Is this maybe an issue with the docker version and api compatibility?
I think i have read somewhere, that the docker version must match 1.13 or something like that?
If i have just installed the newest available Docker, can this be the root cause?