Pfthb

• I've been trying to install Docker registry with basic auth.

It should be connected to a gitlab,latest version-
CentOS Linux release 7.5.1804, 3.10.0-862.14.4.el7.x86_64.
Docker version: 17.05.0-ce, API version: 1.29

• Server set up for Registry is:
  AWS CentOS 6.9, 4.14.77-69.57.amzn1.x86_64.
  Docker version: 18.06.1-ce, API version: 1.38


• Docker is on V2 (Both registry and gitlab)

This works flawlessly:

docker run -d -p 1300:5000 --restart=always --name registry -v /opt/ssl:/opt/ssl -e REGISTRY_HTTP_TLS_CERTIFICATE=/opt/ssl/CERT.crt -e REGISTRY_HTTP_TLS_KEY=/opt/ssl/SRV_KEY.key registry:2

I am able to push, remove and view the images on the web with

https://example.com:1300/v2/_catalog

This is where things starting to get complicated,
I am trying to implement basic Auth onto the registry:

Initially i ran docker run --entrypoint htpasswd registry:2 -Bbn USER PASSWORD > /opt/auth/htpasswd

(Side note, using .htpasswd failed, but using htpasswd worked- Why? why can't i use a hidden file ? docker can't find it although it is actually running with root?)

Then I ran docker run -d -p 1300:5000 --restart=always --name registry -v /opt/ssl:/opt/ssl -e REGISTRY_HTTP_TLS_CERTIFICATE=/opt/ssl/CERT.crt -e REGISTRY_HTTP_TLS_KEY=/opt/ssl/SRV_KEY.key -v /opt/auth:/opt/auth -e "REGISTRY_AUTH=htpasswd" -e "REGISTRY_AUTH_HTPASSWD_REALM=Registry Realm" -e REGISTRY_AUTH_HTPASSWD_PATH=/opt/auth/htpasswd registry:2

(no-auth version of registry was removed off course, also some places suggest to use pwd at the respected location after the -e flag, but that didn't worked- container starts in restarting loop that never ends)

Now, I can login via web to the registry, (Which I assume proves that the auth process works, ?) but the page is blank. dev tools shows http response 200 for the domain, but I get http response 400 for all else.

When trying to login via cli to the registry using:

docker login --username username example.com:1300
||

docker login --username username https://example.com:1300

I get connection refused.

• ALL ports are open.


• password was accepts by the web, so the mechanism is surely working..


• I checked file permission, all was made by root, so who it is not accessible?


• service and container are working and up.

Many sites states that the process I used works, (even on SO) but no real answer on why it is not working.

Any assistance would be most helpful.