Error response from daemon: Get https://registry.gitlab.com/v2/: error parsing HTTP 403 response body: unexpected end of JSON input: “”
A 403 error (not 401) indicates the request was a legal request, but the server is refusing to respond to it. Unlike a 401 Unauthorized response, authenticating will make no difference.
I believe the 403 status code is the result of a container registry failed authentication ban.
GitLab.com responds with HTTP status code
403for 1 hour, if 30 failed authentication requests were received in a 3-minute period from a single IP address.
If you’re still seeing 403 errors, try waiting 1 hour without making any authentication requests to the container registry, and then try again. If the block is removed and the authentication attempt returns a 401 error, check to make sure you’re using the correct username and password/token to authenticate.
Seeing the exact same problem when doing
docker login -u "$CI_REGISTRY_USER" -p "$CI_REGISTRY_PASSWORD" $CI_REGISTRY in my CI pipelie. My Gitlab Docker Registry was working fine as far as I can remember until a while ago (I keep my installation up to date almost weekly). So most likely something changed on Gitlab side as I haven’t touched my Gitlab config. Any clues on how to debug this?