Gitlab Registry Login Timeout using Deploy Token
Summary
When logging into my docker registry using my deploy key, it fails. This is inconsistent, because sometimes it works and sometimes it fails. Definitely not network related.
Steps to reproduce
docker login registry.gitlab.com -u gitlab+deploy-token-XXXXX -p XXXXXXXXXXXXXXXXXXXX
What is the current bug behavior?
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
Error response from daemon: Get https://registry.gitlab.com/v2/: Get https://gitlab.com/jwt/auth?account=gitlab%2Bdeploy-token-XXXXX&client_id=docker&offline_token=true&service=container_registry: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) (Client.Timeout exceeded while awaiting headers)
What is the expected correct behavior?
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
WARNING! Your password will be stored unencrypted in /root/.docker/config.json.
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credentials-store
Login Succeeded
Edited by Werner Raath