Use Gitlab Docker Registry from other software

Description

I was trying to use Gitlab Registry from VMware Admiral ( https://github.com/vmware/admiral ) as a regitry to be able to deploy docker images directly from gitlab registry. It seems that the implementation of Gitlab Registry is somewhat limited and it's not working with this software. Not being able to add the registry server I'm not able to manage docker images and deploy them via this software. The actual workaround is to use another registry for the production images but it would be nice to use the gitlab docker registry as repository.

This is the error I get when trying to add the registry,

Operation for registry https://registry.my.domain:5500 failed: Ping attempts failed with errors: Service https://registry.my.domain:5500/v1/_ping returned error 404 for GET. id 1755412 -- Service https://registry.my.domain/jwt/auth?service=container_registry&scope=registry:catalog:* returned error 403 for GET. id 1755416 

It will also use /v1/search to search for images and some other links.

This is what I see on the registry.log of gitlab:

2017-01-11_16:33:21.43578 127.0.0.1 - - [11/Jan/2017:17:33:21 +0100] "GET /v1/_ping HTTP/1.0" 404 19 "/" "com.vmware.admiral.common.util.ServiceClientFactory"
2017-01-11_16:33:21.43975 time="2017-01-11T17:33:21.439712716+01:00" level=warning msg="error authorizing context: authorization token required" environment=production go.version=go1.5.4 http.request.contenttype="application/json" http.request.host=registry.my.domain http.request.id=a7de1d4a-a603-4cc0-bb2a-dacdd7ee8516 http.request.method=GET http.request.referer="/" http.request.remoteaddr=x.x.x.x http.request.uri="/v2/_catalog?n=1" http.request.useragent=com.vmware.admiral.common.util.ServiceClientFactory instance.id=2d643153-57dc-4a1f-91a6-2f1324a62f3e service=registry version=v2.4.1 
2017-01-11_16:33:21.43978 127.0.0.1 - - [11/Jan/2017:17:33:21 +0100] "GET /v2/_catalog?n=1 HTTP/1.0" 401 134 "/" "com.vmware.admiral.common.util.ServiceClientFactory"
2017-01-11_16:33:21.51476 time="2017-01-11T17:33:21.514700154+01:00" level=warning msg="error authorizing context: insufficient scope" environment=production go.version=go1.5.4 http.request.contenttype="application/json" http.request.host=registry.my.domain http.request.id=a6685dea-95f9-48bb-a191-12622fe1f5d0 http.request.method=GET http.request.referer="/" http.request.remoteaddr=x.x.x.x http.request.uri="/v2/_catalog?n=1" http.request.useragent=com.vmware.admiral.common.util.ServiceClientFactory instance.id=2d643153-57dc-4a1f-91a6-2f1324a62f3e service=registry version=v2.4.1 
2017-01-11_16:33:21.51478 127.0.0.1 - - [11/Jan/2017:17:33:21 +0100] "GET /v2/_catalog?n=1 HTTP/1.0" 401 134 "/" "com.vmware.admiral.common.util.ServiceClientFactory"
Assignee Loading
Time tracking Loading