ii) In Nexus Administration, select Security > Realms. Docker 1.10 and before, the registry client in the Docker Engine only supports Basic Authentication.
From Docker 1.11 the Docker engine supports both Basic Authentication and OAuth2 for getting tokens. i) On the Docker Repository Connector, uncheck the 'Force basic authentication' checkbox. The token server should first attempt to authenticate the client using any authentication credentials provided with the request. "User-Agent": "Docker-Client/17.12.1-ce (linux)"Īnd the ecr-login credentials store then contains the token granting access to ECR. Enabling anonymous authentication allows the Docker client to connect without specifying credentials. What is GitLab CI Runner actually saying with the “no basic auth credentials” error? I assume it doesn’t have credentials, but, where does it look? docker pull works fine via SSH, so why wouldn’t it work here? # cat /etc/gitlab-runner/config.toml docker pull works just fine SSHed into the machine. With the AWS ECS registry comes the need to be logged in, and so I’ve configured the machine with the AWS CLI and run the $(aws ecr get-login -no-include-email) command. What fixed for me: Delete Mac keychain for 'Docker Credentials' and remove any existing aws URLs under auths in /.docker/config. ĮRROR: Preparation failed: API error (500): Get no basic auth credentials Make sure the region you use to log in is the same as the one in your docker image URI. If you’re running Docker micro-services in your Infrastructure, you may be interested in building an internal Private Docker Registry to host Docker images. Using Docker executor with image ***.dkr.ecr.***./***:latest. Our pipelines use images from an AWS ECS registry, and they fail immediately to pull the specified image: Running with gitlab-ci-multi-runner 1.11.5 (cbfcb5c) Our Runner has stopped working and after a day of bashing my head against this I’m no closer to understanding what is going on.