Docker login 401 Unauthorized


#1

Hello ,

I am using nexus as a Docker container, with tag sonatype/nexus3:3.14.0. Also, I connect nexus with LDAP for user better user management it is helpful for group and role management.

For my case, I create a blog-store and create two docker registry repository, one hosted and one group. I try to log in, on hosted and it works fine. But when I tried to connect into the grouped repository I get
401 Unauthorized. I also tried to connect with admin credentials but I get the same error too,

Error response from daemon: login attempt to https:///v2/ failed with status: 401 Unauthorized.

Suggestions are welcome
PParthenis


#2

@pparthenhs

You should check if your access control is set correctly. How do you set access control? Do you use content selectors?


#3

@atselvan

I set up the LDAP correctly. When I am login into nexus UI I can see the grouped Docker registry repository. The problem is when I try to connet into it with docker login command. I get the
following error.

Error response from daemon: login attempt to https://myrepo:port/v2/ failed with status: 401 Unauthorized.

The same problem I am getting when I am try to connect with nexus-admin, which is very odd.


#4

I’m having a similar issue. As per the documentation:

Provide your repository manager credentials of username and password as well as an email address.

I’m never prompted for a email, just a username and password. Does that raise any red flags to anyone?

(also, I’m not using LDAP, just nexus’s built in user management, so LDAP propably isn’t the issue here)


#5

Did anyone find a solution?
I created a simple docker (hosted) repository.
I can see it when I $ curl -X GET http://IP:port/v2/_catalog
But, I cannot login. It keeps rejecting the admin:admin123
I also configured the docker client (/etc/docker/daemon.json) to accept this registry as insecure.
Whatever I do I keep getting the unauthorized.
It is a simple case, it shouldn’t be so hard, don’t you think?


#6

I don’t have any information specific to the problem… but one thing to keep in mind, the communication from docker to nexus looks like this:

Docker Client —> Docker Server —> Neus Repo

So whatever is going wrong here is in between the server and Nexus. Examining the docker daemon logs would be a good idea.


#7

Hi,
Enable the Docker Bearer Token Realm in Nexus Security->Realms Tab.


#8

I did it and it worked.
Thank you very much.

P.S.: Still wondering why there’s nowhere else this information and how all these guys who make tutorial videos don’t say anything about this conf.