Gitlab Docker Registry fails using AWS S3 as backend

[Asier Gomez]

I am trying to configure Gitlab Registry to use AWS S3 as backend to store Docker images.

I have configure like this:

registry['storage'] = {
   's3' => {
     'accesskey' => 'ABCABCABC',
     'secretkey' => 'ABsndjsjdSJSJ',
     'bucket' => 'gitlab-registry',
     'region' => 'eu-west-1'
   }
 }

But when I try to login to the registry:

ikerlan@ikerlan:~$ sudo docker login https://gitlab.prueba.es:4567
Username: asier
Password: 

It throws the next error:

Error response from daemon: Login: {"errors":[{"code":"UNAVAILABLE","message":"service unavailable","detail":"health check failed: please see /debug/health"}]}
 (Code: 503; Headers: map[Server:[nginx] Date:[Fri, 24 Nov 2017 09:33:36 GMT] Content-Type:[application/json; charset=utf-8] Content-Length:[125]])

I just check in some blogs that if you disable the Health checks it could work. But how can I disable the health checks? Any other ideas of the problem?

[Asier Gomez]

I just solved the problem adding a file to the S3 bucket. The problem is that it was a Bug when the S3 bucket is empty, so adding any file to the bucket, the registry works. Then I remove the file and it works perfectly.