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.
El jueves, 30 de noviembre de 2017, 9:12:39 (UTC+1), Asier Gomez escribió:
>
> 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?
>
--
You received this message because you are subscribed to the Google Groups
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to gitlabhq+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/gitlabhq/fa28c599-1f0d-4bb0-bb12-e08f956fafc7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
